Data search & filtering about manacutter HOT 2 OPEN

If you can port existing code, it's probably best to just use ES and consider ripping it out and rewriting it with Lucene after you have something functional out. Just make sure to structure that in a way where transitioning won't be hard to do, of course.

from manacutter.

ES has some major issues that you don't want to overlook:

• Complexlinks can produce fields that are numbers or fields that are objects/arrays, ES will break when indexing a field that switches from primitive to object/array.
• Having an ES server means having to update it at some point, with the post-processed data (provided that you'll have a data processing layer to add some stuff to rows), which kinda defeats the whole "lazy sheets reading" system imo.

I think short term, ES is better because easy to setup and it just works:tm:, but lucene is the way to go if you want to eliminate the boring part of XIVAPI: updating stuff when new update gets released and it's slow af because ES doesn't like super large documents.

from manacutter.