Marc,
We also ran into this problem on updating to Lucene 9.5. We found it
sufficient in our use case to just bump up LRU cache in the constructor to
a high enough value to not pose a performance problem. The default value
of 4k was way too low for our use case with millions of unique facet
valu
A really old example (Lucene 6.x) is here:
https://github.com/lumongo/lumongo/wiki/Distributed-Directory
https://github.com/lumongo/lumongo/tree/master/lumongo-storage/src/main/java/org/lumongo/storage/lucene
But the gist is to extend BaseDirectory and IndexOutput/IndexInput which I
think still ap
Inside of Zulia search engine, the object being indexed is always a
JSON/BSON object and we store the BSON as a stored byte field in the
index. This allows easy internal reindexing when the searchable fields
change but also allows us to update to the latest lucene version.
Combined with using luc
If I understand correctly, I believe you would want to use a TermInSetQuery
query. An example usage can be found here
https://github.com/zuliaio/zuliasearch/blob/main/zulia-server/src/main/java/io/zulia/server/index/ZuliaIndex.java#L398.
You can also check out the usage of KnnVectorQuery here:
h
Thanks Julie. I was able to implement vector search in Zulia with your
pointers. The pull request might be helpful to others:
https://github.com/zuliaio/zuliasearch/pull/70
Thanks,
Matt
On Fri, May 20, 2022 at 9:23 AM Michael Wechner
wrote:
> Hi Julie
>
> I got it running and it seems to work
stributed system around it with sharding/rebalancing?
>
> --
> Regards,
> Alex
>
>
> On Wed, Apr 28, 2021 at 11:18 AM Matt Davis
> wrote:
>
> > Alex,
> >
> > With our lucene based implementation of Zulia (
> > https://github.com/zuliaio/zuliasearch
Alex,
With our lucene based implementation of Zulia (
https://github.com/zuliaio/zuliasearch) we have went back and forth. We
started with Taxonomy and switched and then switched back to taxonomy. In
our experience the Taxonomy based approach is more scalable and
performant. We do large search
With Zulia we chose to rewrite fieldName:* queries to hiddenField:fieldName
and add all field names that are present to a hidden field automatically as
Uwe described as an alternative. It seems to work well.
https://github.com/zuliaio/zuliasearch/blob/master/zulia-query-parser/src/main/java/io/zu
Also can check out https://github.com/zuliaio/zuliasearch for a thinner
approach closer to native lucene or just to see examples of using lucene.
On Wed, Sep 2, 2020, 11:24 AM Alex K wrote:
> FWIW, I agree with Michael: this is not a simple problem and there's been a
> lot of effort in Elasticse
Never used it, but you could look at https://gluonhq.com/products/mobile/.
Also see https://github.com/oracle/graal/issues/373#issuecomment-563435260.
My guess is that Lucene would be a large ask to compile in Graal. REST
services are probably the way to go.
On Fri, Aug 21, 2020 at 10:25 AM Vince
> That is a clever idea. I would still prefer something cleaner but this
> > > could work. Thanks!
> > >
> > > On Sat, Dec 28, 2019 at 10:11 PM Michael Sokolov
> > wrote:
> > >
> > >> I don't know of any pre-existing thing that do
), and then
> appends some special token encoding the length?
>
> On Sat, Dec 28, 2019, 9:36 AM Matt Davis wrote:
>
> > Hello,
> >
> > I was wondering if it is possible to search for the number of tokens in a
> > text field. For example find book titles with 3
hanks,
Matt Davis
ou pulled a new reader and while you are in the process
> of reindexing.
>
> On Sat, Oct 19, 2019 at 1:35 AM Matt Davis
> wrote:
> >
> > Hi All,
> >
> > I am working on implementing of an in place reindex using Lucene. In my
> > case, I have BSON document sto
Hi All,
I am working on implementing of an in place reindex using Lucene. In my
case, I have BSON document stored in a binary field and have a set of rules
that pull fields out of the BSON and indexes them into different Lucene
fields with different analyzers. I would like to be able to change t
15 matches
Mail list logo
