So no one knows this then?
It seems like a good opportunity to get some performance!
On Tue, Feb 25, 2020 at 2:01 PM S G wrote:
> Hi,
>
> I see a lot of such queries in my Solr 7.6.0 logs:
>
>
> *path=/select
> params={q=*:*=false=_docid_+asc=0=javabin=2}
> hits=287128180 status=0 QTime=7173*
>
Given a docId if I call advanceExact(docId) and if this will return true.
Can I call
https://github.com/apache/lucene-solr/blob/releases/lucene-solr/8.4.1/lucene/core/src/java/org/apache/lucene/index/NumericDocValues.java#L32-L35
to retrieve the value?
If YES I am fine with it if NO what
Ah yes, Java interface default implementation methods were introduced in
Java 8. I need to add support for this feature...
Thank you for the bug report !
Andi..
On Wed, 26 Feb 2020, Petrus Hyvönen (Jira) wrote:
[
Erick, I opened a JIRA for this:
https://issues.apache.org/jira/browse/SOLR-14293
Thanks!
Ivan
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
On Friday, February 28, 2020, 09:02:12 AM PST, Ivan Provalov
wrote:
Thanks, Erick! Understood.
On Friday, February 28, 2020, 08:24:45 AM PST, Erick Erickson
wrote:
Ivan:
Long time!
If the test fails against 8x or master, certainly raise a JIRA. But there’s
little
--
Good Day
You have been nominated to receive a Grant Fund. Kindly email
"jenusalon...@gmail.com" for further information.
Use Reference Number "LSDSO/3828/14-E” as your email subject.
Sincerely,
Public Relations
LSDS Organization
Thanks, Erick! Understood.
On Friday, February 28, 2020, 08:24:45 AM PST, Erick Erickson
wrote:
Ivan:
Long time!
If the test fails against 8x or master, certainly raise a JIRA. But there’s
little chance there’ll be a release of 6x.
Best,
Erick
> On Feb 28, 2020, at 12:45 AM,
Ivan:
Long time!
If the test fails against 8x or master, certainly raise a JIRA. But there’s
little chance there’ll be a release of 6x.
Best,
Erick
> On Feb 28, 2020, at 12:45 AM, Ivan Provalov
> wrote:
>
> I noticed a weird payload behavior with Solr 6.3.0. After writing the
>
Alan,
Thank you for taking your time to look at this. Nice catch. I was using a
copy of the org.apache.lucene.index.TestPayloads.
I made the necessary changes to the analyzer to address this: I use non-mocked
tokenizer and a new filter which would create a random payload (see attached).
I just wanted to pick this up, but somehow my JIRA account got
deactivated. Once I have that figured out, I'll try to propose the
change. Thank you!
On 28.02.20 14:13, David Smiley wrote:
Thanks for your input David. I won't accept the patch because I think
there's a more appropriate way
Thanks for your input David. I won't accept the patch because I think
there's a more appropriate way to go about this -- have the Tagger
constructor take an Analyzer instead of a TokenStream in the constructor,
and then have the process method take the InputStream and/or string (the
fundamental
Your TokenStreamComponents object is getting re-used, so only the first
PayloadData object gets referenced by the PayloadFilter.
> On 28 Feb 2020, at 06:55, Ivan Provalov wrote:
>
> I tested these versions and I can reproduce for each one:
>
> v6.3.0
> v7.7.2
> v8.3.1
>
>
>
>
You’re dealing with cases where the document in question doesn’t have a value
in the iterator. So `advance(doc)` will return a docId greater than doc, as it
moves to the next doc that does have a value, and `advanceExact(doc)` returns
`false` because you can’t do an exact advance to a value
On 27.02.20 19:01, David Smiley wrote:
I'm glad you got it working! It's sad you felt the need to copy-paste
the tagger; perhaps you can recommend changes to make it more extensible
so that you or others needn't fork it.
Don't need to feel sad, just as I mentioned: it's quick, dirty and I
14 matches
Mail list logo
