Property 'length' of undefined when using web-worker about flexsearch HOT 9 CLOSED

I found out that using workers when indexing documents (instead of id-content-pairs) did not work actually. Workers needs a re-implementation to split threads through document fields.

from flexsearch.

@ts-thomas I was on an earlier version (v0.6.22) instead of latest, where workers weren't working for me even with id-content-pairs. However, using the latest and the callback version of search(), I can get it to work now.

from flexsearch.

Hello thanks for the report. The problem is that worker have some missing functionality of handling documents. I'm trying to provide a fix for this as soon as possible.

from flexsearch.

Also looking for this. If you push this further onto the roadmap, let me know, as I can try being of help. Thx.

from flexsearch.

Current state

I have added most of the missing features that worker needs to handle documents. During this changes I also added a new distribution model between worker instances to support multi-field-search in parallel (that's a big plus). It has turned out that this distribution is not easy to solve. But I'm optimistic that this will be ready very soon.

from flexsearch.

Great package!

I have a pretty big json document I want to search, and was wondering if Web workers are even working at all, since they would speed things up it seems.

I am trying to get search via web workers working, but I keep getting undefined search results whenever I set the worker to an integer, which seems similar to this issue.

I tried using the example in the documentation, but that doesn't seem to be working (on jsbin or my local project).

`var index = new FlexSearch({
encode: "icase",
tokenize: "full",
async: true,
worker: 4
});

index.add(10025, "John Doe");

index.search("John Doe", function(results){
console.log(results) // undefined
});

index.search("John Doe").then(function(results){
console.log(results)// undefined
});`
I would expect it to return an array with 10025.

Is there an extra step somewhere that i'm missing?

from flexsearch.

I'm seeing roughly the same thing as @valdrox, except instead of getting undefined back, I get an empty array ([]).

from flexsearch.

Please notice, that Workers does not work within Node.js, it is just available through a Browser. Running multiple instances in Node.js is basically implemented in FlexSearch-Server. I need to move this capability to the client to make a Worker-fallback available in Node.js

from flexsearch.

Please change over to the version >= 0.7.x, thanks a lot.

from flexsearch.