Hi David,
Thank you very much for your revert. Just one query SOLR embedded zookeeper
will require JAVA server VM or Java Client VM?
Thanks,
Shilvi
From: David Smiley
Sent: 26 February 2020 23:07
To: Solr/Lucene Dev
Subject: Re: Query - SOLR 1.0
This message originated from outside our
Hello!
I've wanted to create a JIRA Ticket, but the interface asked me to
discuss this here, which seems fine as well.
Assumptions (which might as well false):
The package management/plugin infrastructure allows me to add plugin
jars via several options. Since expressibles only work in
We will not answer user questions on the development list. Please respect
David’s request to move your questions to solr-u...@lucene.apache.org mailing
list.
Jan
> 27. feb. 2020 kl. 10:20 skrev shilvi.par...@barclays.com.invalid
> :
>
> Hi David,
>
> Thank you very much for your revert.
Hello again!
On 25.02.20 22:39, David Smiley wrote:
I haven't worked on streaming expressions yet but I did a little bit of
digging around. I think the ClassifyStream might be somewhat similar to
learn from. It takes a stream of docs, not unlike what you want. And
crucially it implements
I tested these versions and I can reproduce for each one:
v6.3.0
v7.7.2
v8.3.1
org.apache.lucene
lucene-test-framework
8.3.1
For 8.3.1, you will need to change MultiFields.getTermPositionsEnum(...) to
MultiTerms.getTermPostingsEnum(...).
On Thursday,
I noticed a weird payload behavior with Solr 6.3.0. After writing the
Lucene62Codec specific unit test (attached) I think there could be a bug which
allows for the same term payloads to be written into another document's same
term payload (or the second payload for the second document being
Thanks for reporting bugs.
I checked the Reference Guide and the documentation seems correct:
https://lucene.apache.org/solr/guide/8_4/spell-checking.html#spell-check-parameters
In fact that parameter was only added to the documentation from version 7.3.
Please specify exactly which
Eric,
On 27.02.20 14:40, Eric Pugh wrote:
David, I know I’d love to see the code!
Here you go. Not pretty, but it works.
https://github.com/einsweniger/SolrStreamTagger/
This is not how I plan to do this upstream, just if somebody looks at it.
regards,
David
Hello,
I'd like sharing an error in the documentation of Solr related to
SpellCheck.
I was investigating why the parameter spellcheck.queryAnalyzerFieldtype wasn't
working and I saw that type was lowercase in the documentation. The correct
should be spellcheck.queryAnalyzerFieldType
Hope to be
David, I know I’d love to see the code!
I’ve been working on streaming expression called “bump” that triggers a atomic
update reindex process on a document. I’m using it as part of a relevancy
experimentation workflow where I add a new copyField or change my schema
analyzers, and then I
David, I think our efforts are running in parallel, as yesterday I did the
exact same thing as you!!!
The good news is that if you are on unreleased 8.5, the add-expressible
works!!! I spent some time tearing my hair out working with Master, and then
8.4.1, and then finally moved over to
Hey, Whatsup?
On Thu, Feb 27, 2020 at 9:35 PM Apache Jenkins Server <
jenk...@builds.apache.org> wrote:
> Build: https://builds.apache.org/job/Lucene-Solr-Tests-master/4353/
>
> All tests passed
>
> Build Log:
> [...truncated 68080 lines...]
> BUILD FAILED
>
Also, Noble and I have been working on trying to get expressibles to work
with the new package manager. Will put some samples together soon.
On Thu, 27 Feb, 2020, 7:20 pm Eric Pugh,
wrote:
> David, I think our efforts are running in parallel, as yesterday I did the
> exact same thing as you!!!
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.
I'm not sure if something like this should be contributed back to Solr
itself. I don't even know the bigger
Hi guys!
I am a newbie and I am trying to upgrade from Lucene 6.2.1 to 8.4.1
The previous code was leveraging this
https://github.com/apache/lucene-solr/blob/releases/lucene-solr/6.2.1/lucene/core/src/java/org/apache/lucene/index/NumericDocValues.java#L34
now
I changed the code to return a default value instead of an exception. In case
the doc will not be found.
I would like really to understand better why we have such comment in that
iterator
* Returns the numeric value for the current document ID. * It is illegal
> to call this method after
16 matches
Mail list logo