Andrei, it's not clear what's the problem, but if you need to join children
to parents and then select only subset of parents you need to combine join
with parent filter. Some cases are explained
https://lucene.apache.org/solr/guide/8_0/other-parsers.html#OtherParsers-BlockJoinParentQueryParser
.
So you are implying that the parent filter allows subsets. The code at
https://github.com/apache/lucene-solr/blob/master/lucene/join/src/java/org/apache/lucene/search/join/CheckJoinIndex.java#L46
implies that subset is not allowed. If I select a subset and invoke the
checker, I get this IllegalS
Of course if it were the case, but since the data is there for the third
and fourth, it should have brought the related data.
Best regards
On 7/5/19 10:27 AM, Atri Sharma wrote:
Should not matter, AFAIK.
If your first MUST clause in a BooleanQuery fails to match for a
document, then there is
Should not matter, AFAIK.
If your first MUST clause in a BooleanQuery fails to match for a
document, then there is no point for the engine to match further
clauses, right?
On Fri, Jul 5, 2019 at 7:56 PM wrote:
>
> Re-sending and please let me know Your amazing thoughts
>
> Happy July 4th
>
> Bes
Re-sending and please let me know Your amazing thoughts
Happy July 4th
Best regards
On 7/3/19 6:01 PM, baris.ka...@oracle.com wrote:
Hi,-
does it matter which field is added first into index when multi field
Lucene is used?
does that make difference at search time like if it matches firs
