finer grained setting.
* AND junctions probably it probably shouldn’t be applied at an index level
* OR junctions could as it’s a union
Combinations of the two or ancestor nodes should be smarter but that requires
additional changes to make elegant…
From: Jason Huynh
Date: Tuesday, Marc
rio
____
Šalje: Jason Huynh
Poslano: 15. ožujka 2022. 21:11
Prima: dev@geode.apache.org
Predmet: Re: Question about INDEX_THRESHOLD_SIZE
Additional thought:
It would be nice to set/check CAN_APPLY_LIMIT_AT_INDEX on a per node basis or
at least a finer grained s
should be smarter but that requires
additional changes to make elegant…
From: Jason Huynh
Date: Tuesday, March 15, 2022 at 1:03 PM
To: dev@geode.apache.org
Subject: Re: Question about INDEX_THRESHOLD_SIZE
Hi Mario,
Digging a little bit more, I’m assuming the CompiledLike probably should
,
-Jason
From: Mario Kevo
Date: Monday, March 14, 2022 at 8:17 AM
To: dev@geode.apache.org
Subject: Odg: Question about INDEX_THRESHOLD_SIZE
Hi,
Regarding Anil's answer:
The test will pass as we have set INDEX_THRESHOLD_SIZE to 1000 (that is how
many entries are in the region). If you del
apache.org
Predmet: Re: Question about INDEX_THRESHOLD_SIZE
As an fyi, in the past we disabled applying limits at the index level for range
indexes.
I’m surprised in this case that we would add all the entries to the
intermediate results instead of applying the filter first and checking the
through the code, perhaps it’s hitting a different
index type (I’d think a map index but that probably is backed by
CompactRangeIndexes for each key…)
From: Jason Huynh
Date: Friday, March 11, 2022 at 12:47 PM
To: dev@geode.apache.org
Subject: Re: Question about INDEX_THRESHOLD_SIZE
I think https://g
h index:
gfsh>query --query="SELECT e.key, e.value from
/example-region.entrySet e where e.value.positions['SUN'] like 'someth%'"
Result : true
Limit : 100
Rows: 0
Query Trace : Query Executed in 8.784831 ms; indexesUsed(1):
sh>query --query="SELECT e.key, e.value from
/example-region.entrySet e where e.value.positions['SUN'] like 'someth%'"
Result : true
Limit : 100
Rows: 0
Query Trace : Query Executed in 8.784831 ms; indexesUsed(1):index1(Results:
100)
.value from /example-region.entrySet
e where e.value.positions['SUN'] like 'someth%'"
Result : true
Limit : 100
Rows : 0
Query Trace : Query Executed in 8.784831 ms; indexesUsed(1):index1(Results: 100)
BR,
Mario
Šalje: Anil
Mario,
There are few changes happened around this area as part of GEODE-9632 fix; can
you please revert that change and see if the query works both with and without
index.
Looking at the code; it seems to restrict the number index look up that needs
to be performed; certain latency/throughput
Hi geode-dev,
Some time ago I was working on allowing INDEX_THRESHOLD_SIZE System property to
override CompiledValue.RESULT_LIMIT.
After this change, adding this attribute will take into a count if you set it.
But I need some clarification of this INDEX_THRESHOLD_SIZE attribute. Why is
this set
11 matches
Mail list logo
