Adding positionIncrementGap="1" to the fields worked for me. I didn't
re-index all the existing docs so it works for only future documents.
On Mon, Apr 28, 2014 at 3:54 PM, Ahmet Arslan wrote:
>
>
> Hi Vijay,
>
> It is a index time setting so yes solr restart and re-indexing is
> required. So
Hi Vijay,
It is a index time setting so yes solr restart and re-indexing is required. So
A small test case would be handy
On Tuesday, April 29, 2014 1:35 AM, Vijay Kokatnur
wrote:
Thanks Ahmet, I'll give that a try. Do I need to re-index to add/update
positionIncrementGap?
On Mon, Apr
I tried testing with positionIncrementGap but that didn't work. The values
I passed for it were 0, 1, 4,100.
Reindexing also didn't help.
On Mon, Apr 28, 2014 at 3:34 PM, Vijay Kokatnur wrote:
> Thanks Ahmet, I'll give that a try. Do I need to re-index to add/update
> positionIncrementGap?
>
Thanks Ahmet, I'll give that a try. Do I need to re-index to add/update
positionIncrementGap?
On Mon, Apr 28, 2014 at 3:31 PM, Ahmet Arslan wrote:
> Hi,
>
> I would add positionIncrementGap to fieldType definitions and experiment
> with different values. 0, 1 and 100.
>
>
> positionIncrementG
Hi,
I would add positionIncrementGap to fieldType definitions and experiment with
different values. 0, 1 and 100.
Same with OrderLineType too
On Tuesday, April 29, 2014 1:25 AM, Vijay Kokatnur
wrote:
Hey Ehmet,
Here is the field def -
On Mon, Apr 28, 2014 at 3:19 PM, Ahme
Hey Ehmet,
Here is the field def -
On Mon, Apr 28, 2014 at 3:19 PM, Ahmet Arslan wrote:
> Hi,
>
> Can you paste your field definition of BookingRecordId and OrderLineType?
> It could be something related to positionIncrementGap.
>
> Ahmet
>
>
>
> On Tuesday, April 29, 2014 12:58 AM,
Hi,
Can you paste your field definition of BookingRecordId and OrderLineType? It
could be something related to positionIncrementGap.
Ahmet
On Tuesday, April 29, 2014 12:58 AM, Ethan wrote:
Facing the same problem!! I have noticed it works fine as long as you're
looking up the first index pos
Facing the same problem!! I have noticed it works fine as long as you're
looking up the first index position.
Anyone faced similar problem before?
On Mon, Apr 28, 2014 at 12:22 PM, Vijay Kokatnur
wrote:
> I have been working on SpanQuery for some time now to look up multivalued
> fields and fou
I have been working on SpanQuery for some time now to look up multivalued
fields and found one more issue -
Now if a document has following lookup fields among others
"*BookingRecordId*": [ "100268421", "190131", "8263325" ],
"*OrderLineType*": [ "13", "1", "11" ],
Here is the query I construc
