You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@lucenenet.apache.org by Haberl Norbert <No...@ssi-schaefer.com> on 2017/05/10 08:43:21 UTC
Usage of MemoryIndex
Hi,
would like to ask if anybody has an example of how we could use the MemoryIndex?
Would need a fast way of lookup data in an autocomplete control on a website (1 mio datasets).
As I understand I cannot store any data inside MemoryIndex so what is the sense behind?
Is RAMIndex what I am looking for or at least I have to look for?
Thanks!
Best regards,
Norbert Haberl | Software Engineer | Customer Service & Support
RE: Usage of MemoryIndex
Posted by Shad Storhaug <sh...@shadstorhaug.com>.
We have not yet generated API documentation (contributions welcome), but the packages have XML documentation that enables Intellisense support. You may find the Java API documentation for Suggest helpful: https://lucene.apache.org/core/4_8_0/suggest/index.html
-----Original Message-----
From: Haberl Norbert [mailto:Norbert.Haberl@ssi-schaefer.com]
Sent: Wednesday, May 10, 2017 4:39 PM
To: user@lucenenet.apache.org
Subject: AW: Usage of MemoryIndex
Thanks, is there any documentation about the suggestion package ?
Found nothing on Github
Best regards,
Norbert Haberl | Software Engineer | Customer Service & Support Phone +43 316 6096 - 8435 SSI SCHÄFER | SSI Schäfer Automation GmbH | Fischeraustraße 27 | 8051 Graz | Austria
Norbert.Haberl@ssi-schaefer.com
Website | Blog | YouTube | Facebook
-----Ursprüngliche Nachricht-----
Von: itamar.synhershko@gmail.com [mailto:itamar.synhershko@gmail.com] Im Auftrag von Itamar Syn-Hershko
Gesendet: Mittwoch, 10. Mai 2017 11:18
An: user@lucenenet.apache.org
Betreff: Re: Usage of MemoryIndex
RAMIndex would be more appropriate, yes, although on-disk indexes will also perform fairly well
MemoryIndex is a single-document index, used mostly for alerting-type usages where you want to check thousands or more of queries against a single document. See http://lucene.apache.org/core/4_8_0/memory/org/apache/lucene/index/memory/MemoryIndex.html
For auto-complete you should also look at the suggesters package here https://github.com/apache/lucenenet/tree/master/src/Lucene.Net.Suggest/Suggest
--
Itamar Syn-Hershko
Freelance Developer & Consultant
Elasticsearch Partner
Microsoft MVP | Lucene.NET PMC
http://code972.com | @synhershko <https://twitter.com/synhershko> http://BigDataBoutique.co.il/
On Wed, May 10, 2017 at 11:43 AM, Haberl Norbert < Norbert.Haberl@ssi-schaefer.com> wrote:
> Hi,
>
> would like to ask if anybody has an example of how we could use the
> MemoryIndex?
> Would need a fast way of lookup data in an autocomplete control on a
> website (1 mio datasets).
>
> As I understand I cannot store any data inside MemoryIndex so what is
> the sense behind?
> Is RAMIndex what I am looking for or at least I have to look for?
>
> Thanks!
>
> Best regards,
> Norbert Haberl | Software Engineer | Customer Service & Support
>
AW: Usage of MemoryIndex
Posted by Haberl Norbert <No...@ssi-schaefer.com>.
Thanks, is there any documentation about the suggestion package ?
Found nothing on Github
Best regards,
Norbert Haberl | Software Engineer | Customer Service & Support
Phone +43 316 6096 - 8435
SSI SCHÄFER | SSI Schäfer Automation GmbH | Fischeraustraße 27 | 8051 Graz | Austria
Norbert.Haberl@ssi-schaefer.com
Website | Blog | YouTube | Facebook
-----Ursprüngliche Nachricht-----
Von: itamar.synhershko@gmail.com [mailto:itamar.synhershko@gmail.com] Im Auftrag von Itamar Syn-Hershko
Gesendet: Mittwoch, 10. Mai 2017 11:18
An: user@lucenenet.apache.org
Betreff: Re: Usage of MemoryIndex
RAMIndex would be more appropriate, yes, although on-disk indexes will also perform fairly well
MemoryIndex is a single-document index, used mostly for alerting-type usages where you want to check thousands or more of queries against a single document. See http://lucene.apache.org/core/4_8_0/memory/org/apache/lucene/index/memory/MemoryIndex.html
For auto-complete you should also look at the suggesters package here https://github.com/apache/lucenenet/tree/master/src/Lucene.Net.Suggest/Suggest
--
Itamar Syn-Hershko
Freelance Developer & Consultant
Elasticsearch Partner
Microsoft MVP | Lucene.NET PMC
http://code972.com | @synhershko <https://twitter.com/synhershko> http://BigDataBoutique.co.il/
On Wed, May 10, 2017 at 11:43 AM, Haberl Norbert < Norbert.Haberl@ssi-schaefer.com> wrote:
> Hi,
>
> would like to ask if anybody has an example of how we could use the
> MemoryIndex?
> Would need a fast way of lookup data in an autocomplete control on a
> website (1 mio datasets).
>
> As I understand I cannot store any data inside MemoryIndex so what is
> the sense behind?
> Is RAMIndex what I am looking for or at least I have to look for?
>
> Thanks!
>
> Best regards,
> Norbert Haberl | Software Engineer | Customer Service & Support
>
Re: Usage of MemoryIndex
Posted by Itamar Syn-Hershko <it...@code972.com>.
RAMIndex would be more appropriate, yes, although on-disk indexes will also
perform fairly well
MemoryIndex is a single-document index, used mostly for alerting-type
usages where you want to check thousands or more of queries against a
single document. See
http://lucene.apache.org/core/4_8_0/memory/org/apache/lucene/index/memory/MemoryIndex.html
For auto-complete you should also look at the suggesters package here
https://github.com/apache/lucenenet/tree/master/src/Lucene.Net.Suggest/Suggest
--
Itamar Syn-Hershko
Freelance Developer & Consultant
Elasticsearch Partner
Microsoft MVP | Lucene.NET PMC
http://code972.com | @synhershko <https://twitter.com/synhershko>
http://BigDataBoutique.co.il/
On Wed, May 10, 2017 at 11:43 AM, Haberl Norbert <
Norbert.Haberl@ssi-schaefer.com> wrote:
> Hi,
>
> would like to ask if anybody has an example of how we could use the
> MemoryIndex?
> Would need a fast way of lookup data in an autocomplete control on a
> website (1 mio datasets).
>
> As I understand I cannot store any data inside MemoryIndex so what is the
> sense behind?
> Is RAMIndex what I am looking for or at least I have to look for?
>
> Thanks!
>
> Best regards,
> Norbert Haberl | Software Engineer | Customer Service & Support
>