Hi
We want to index and search hex numbers (including hex ranges) in Lucene.
We are using Lucene 5.3.1
I could find only Int and long but not hex.
My hex numbers are IPV6 excluding colon. Long can not hold such big hex
numbers.
What could be the possible solution to this.
Regards
Rajnish
Hi
How are indexed and stored fields treated by Lucene w.r.t space and
performance?
Is there any performance hit with stored fields which are indexed?
Lucene Version: 5.3.1
Assumption:
Stored fields are just simple strings (not huge documents)
Example:
Data: [101, Gold]; [102, Silver
}(not(exists(field3))
> On Saturday, July 15, 2017, 1:01:04 PM GMT+3, Rajnish kamboj <
> rajnishk7.i...@gmail.com> wrote:
>
>
> Ok, I will check.
>
> On Sat, 15 Jul 2017 at 3:26 PM, Ahmet Arslan wrote:
>
> > Hi,
> >
> > Yes, here it is: q=+*:* -field3:
Ok, I will check.
On Sat, 15 Jul 2017 at 3:26 PM, Ahmet Arslan wrote:
> Hi,
>
> Yes, here it is: q=+*:* -field3:[* TO *]
>
> Ahmet
>
> On Saturday, July 15, 2017, 8:16:00 AM GMT+3, Rajnish kamboj <
> rajnishk7.i...@gmail.com> wrote:
>
>
> Hi
> Does Luc
Hi
Does Lucene provide any API to fetch documents for which a field is not
defined.
Example
Document1 : field1=value1, field2=value2,field3=value3
Document2 : field1=value4, field2=value4
I want a query to get documents for which field3 is not defined. In example
it should return Document2.
Reg
he.org/jira/browse/LUCENE-7055
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
>
> On Fri, Jan 6, 2017 at 2:28 AM, Rajnish kamboj
> wrote:
> > OK, got it
> >
> > One thing still I need to know (which is not clear to me)
> > How does
t; What about writing your own scoring that just give a value of 1 to all
> the
> > documents that are hits?
> >
> > On Mon, Jan 9, 2017 at 12:17 PM, Rajnish kamboj <
> rajnishk7.i...@gmail.com >
> > wrote:
> >
> > > My application does not require sco
My application does not require scoring/ranking. All data is equally
important for me.
Search query can return any documents matching search criteria.
So, Is there a way to completely disable scoring/ranking altogether?
OR Is there a better solution to it.
Regards
Rajnish
We being new to Lucene are struggling hard to dimension our application
w.r.t search throughput
As stated by "Mike McCandless" in the following thread, we had ran our
cases with restrictive data set also.
http://mail-archives.apache.org/mod_mbox/lucene-java-user/201701.mbox/raw/%3CCAL8Pwka4RC3c%2B%
that I
can benchmark my application throughput?
Regards
Rajnish
On Tue, Jan 3, 2017 at 6:09 PM, Rajnish kamboj
wrote:
> OK, got it
>
> One thing still I need to know (which is not clear to me)
> How does Lucene calculates the most restrictive clause?
>
> Correct me, i
v. 2017 à 12:52, Rajnish kamboj a
> écrit :
>
> > High CPU may be ideal, but 100% CPU utilization is not ideal. (We might
> be
> > missing very silly thing)
> >
> > More information on our environment:
> > Machine details: 4 vCPUs and 4 GB RAM
> > Search Lo
our data set to 25000, still CPU usage was very high, but
throughput increases.
Please advice, if we are missing any Lucene recommendations?
On Tue, Jan 3, 2017 at 1:04 AM, Trejkaz wrote:
> On Tue, Jan 3, 2017 at 5:26 AM, Rajnish kamboj
> wrote:
> >
> > Hi
> >
> &g
My guess: more conditions = less documents to score and sort to return.
>
> On Mon, Jan 2, 2017 at 7:23 PM, Rajnish kamboj
> wrote:
>
> > Hi
> >
> > Is there any Lucene performance benchmark against certain set of data?
> > [i.e Is there any stats for search throughp
Hi
The CPU usage goes upto 100% during search.
We were using RAM Directory, but later switched to MMap Directory.
The CPU usage remains between 90-100%.
Is it obvious that the CPU usage remain high during Lucene search or we are
missing something?
Our data set was only 3.5 Million records (~ 2 G
Hi
Is there any Lucene performance benchmark against certain set of data?
[i.e Is there any stats for search throughput which Lucene can provide for
a certain data?]
Search throughput Example:
Max. 200 TPS for 50K data on Lucene 5.3.1 on RHEL version x (with SSD)
Max. 150 TPS for 100K data on Luc
Hi
Is it advisable to store and index values of different datatype under same
field as follows
Field field = new LongField("*region*", 10L, Field.Store.YES);
doc.add(field);
Field field1 = new StringField("*region*", "NORTH", Field.Store.YES);
doc.add(field1);
Our field "region" can have numeric
Any thought on the below question?
On Friday 14 October 2016, Rajnish Kamboj wrote:
> Hi
>
> How can I make my Lucene queries agnostic to Lucene Versions?
>
> e.g. NumericRangeQuery in 5.3.1 is LegacyNumericRangeQuery in 6.0.0
> (NumericRangeQuery is completely removed)
>
>
>
> --
> Rajnish
>
Hi
Is there any performance gain of writing Lucene queries (query objects)
rather than parsing Lucene query strings using QueryParser. I believe
parser has its own overhead.
Example:
Term lTerm1 = new Term("rs", "997101");
Term uTerm1 = new Term("rs", "997104");
TermRangeQuery trQuery1 =
Hi
Performance of Prefix, Wildcard and Regex queries?
Does Lucene internally optimizes this (using rewrite or something else) or
I have to manually create specific queries depending on input pattern.
Example
if input is 78* create Prefix query
if input is 87?98* create Wildcard query
if input is
Hi
How can I make my Lucene queries agnostic to Lucene Versions?
e.g. NumericRangeQuery in 5.3.1 is LegacyNumericRangeQuery in 6.0.0
(NumericRangeQuery is completely removed)
--
Rajnish
ing a PrefixTermsEnum.
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
>
> On Tue, Sep 13, 2016 at 11:25 AM, Rajnish kamboj
> > wrote:
> > Hi
> >
> > How can I get all matched terms of a document in PrefixQuery?
> >
> > Term t2 = n
Hi
How can I get all matched terms of a document in PrefixQuery?
Term t2 = new Term("contents", "br");
PrefixQuery query = new PrefixQuery(t2);
Suppose I have few documents with 1000 different terms.
Search is showing me the document in which it find the br words.
Now, how can I get all the br
thetaphi.de
>
> > -Original Message-
> > From: Rajnish kamboj [mailto:rajnishk7.i...@gmail.com ]
> > Sent: Monday, August 22, 2016 5:22 PM
> > To: java-user@lucene.apache.org
> > Subject: Re: searchAfter behavior after reindexing
> >
> > Please help m
Please help me in understanding the behaviour of searchAfter().
On Sunday 21 August 2016, Rajnish kamboj wrote:
> Hi Team
>
> What is the searchAfter behavior if index is continuously being updated.
> Document numbers changes if indexes are updated. Also indexes are update
> o
Hi Team
What is the searchAfter behavior if index is continuously being updated.
Document numbers changes if indexes are updated. Also indexes are update on
segment merge.
Now, Suppose
- I am holding a ScoreDoc before index update
- Index is updated (document number changes).
(A document
25 matches
Mail list logo