Hi Joel,
Thanks for the information.
Regards,
Edwin
On 25 March 2017 at 10:15, Joel Bernstein wrote:
> The innerJoin is a merge join and the hashJoin is a hash join.
>
> The merge join can support joins of unlimited size and never runs out of
> memory. But it requires that both sides of the j
I would consider this a bug. Collapse has never really been tested with
export. But this would certainly speed up the unique Streaming Expression.
Joel Bernstein
http://joelsolr.blogspot.com/
On Fri, Mar 24, 2017 at 7:46 AM, David Svånå wrote:
> Hello,
>
> Summary: when using export handler wit
Hello,
I have a problem with ComplexPhrase and TurkishLowerCaseFilterFactory.
When I search like {!complexphrase}SContent_tinx:"6* YAŞINDA",
{!complexphrase}SContent_tinx:"6* yaşında", results is correct.
{ "responseHeader":{ "zkConnected":true, "status":0, "QTime":104, "params":{
"q":"{!complex
Hi,
I am trying to integrate UIMA with Solr.
I have created the pear file(packaged and installed)-
opennlp.uima.OpenNlpTextAnalyzer_pear.xml
I am using openNLP -uima annotators for document analysis.
The pear(xml) file is located at
path:D:\temp\opennlp.uima.OpenNlpTextAnalyzer
*folder structure
Hello
It sounds similar to
https://lucidworks.com/2011/11/29/whats-with-lowercasing-wildcard-multiterm-queries-in-solr/
(yep, I see TurkishLowerCaseFilterFactory there)
What's your analyzer for this field? Does it work for plain wildcards
queries? I'm asking because CPQP adds an oddity sometimes.
Mikhail:
I just checked and I don't think CPQP is passing the terms through the
lowercase filter when it's a phrase. I used the text_tr fieldType in
the techproducts schema and get these relevant bits:
q=eoe:YASIN*
parsedquery: "eoe:yasın*"
q={!complexphrase}eoe:YASIN*
parsedquery: "eoe:yasın*"
I think we figure out the issue, When we were conventing delete by query in
a Solr Handler we were not making a deep copy of BytesRef. We were making
reference of same object, which was causing old deletes(LinkedHasmap)
adding more than 1K entries.
But I think it is still not clearing those 1K ent
Hi
My fieldType definition is below. When I search without
ComplexPhraseQueryParser, numbers of results are same for "60 YAŞIND*" and "60
yaşınd*".
{ "responseHeader":{ "zkConnected":true, "status":0, "QTime":5, "params":{ "
q":"60 YAŞIND*", "indent":"on", "rows":"0", "wt":"json", "_":"14904565
Hello:
I'm interested in querying solr as a spark rdd. Has anyone used the
lucidworks code api https://github.com/lucidworks/spark-solr to issue
multiple queries? I'd like to have it execute multiple queries and
have the top n results be combined into one spark rdd for further
analysis. The exam
