Hi,
could someone please unsubscribe me? I tried unsubscribing through
java-user-unsubscr...@lucene.apache.org several times.
Thanks!
Martine
We have been having a very long discussion many issues are posed, thank you
everyone who is involved.
Here is a short, non-exhaustive summary of posed issues/questions (with my
brief thoughts/opinions) so far.
* Concerns for political neutrality of GitHub - in other words, concerns
for account
On Wed, May 25, 2022 at 2:08 PM Greg Miller wrote:
>
>
> I guess with an “unsorted” numeric DV type we could get there with aligned
> indices, as you describe, but that seems less appealing than supporting
> multi-dim points directly.
>
Name one technical reason why?
Unsorted would be exactly
Read your example again and yes, that makes sense. I was only thinking in
terms of single dimensions, my bad!
On Wed, May 25, 2022 at 11:08 AM Greg Miller wrote:
> I appreciate all the feedback, but disagree that we can accomplish what
> we’re trying to do here with the existing fields.
>
>
I appreciate all the feedback, but disagree that we can accomplish what
we’re trying to do here with the existing fields.
It’s not sufficient to AND together multiple fields for this use-case
because of the fact that the different dimensions can be multi-valued and
not all combinations are valid.
>
> But adding a new type should be the last resort.
I did not realize that was the case, that's good to know. It seems like I
should just use BDV (which does make the code change easier/faster so I
have no issues with it).
As for Patrick's suggestion of using separate numeric fields instead of
On Wed, May 25, 2022 at 12:17 AM Greg Miller wrote:
>
> A "two separate field approach" would
> consist of indexing year and make separately, and you'd lose the
> information that only certain combinations are valid. Am I overlooking
> something with your suggestion? Maybe there's something we
> then use LatLonDocValuesField
Right! Actually, LatLonDocValuesField is a good example of what we're
trying to do here, but specialized to the 2D, lat/long case. It stores
a doc value representation of a lat/long point that can be used for
"slow" queries—which complement the points-based
On Wed, May 25, 2022 at 8:04 AM Michael Sokolov wrote:
>
> Also, there should be examples from other fields. Suppose you are
> indexing map data and want to support a UI that shows "hot spots" on
> the map where there is a lot of let's say ... activity of some sort.
> You'd like to facet on 2-d
Also, there should be examples from other fields. Suppose you are
indexing map data and want to support a UI that shows "hot spots" on
the map where there is a lot of let's say ... activity of some sort.
You'd like to facet on 2-d areas.
Or for log analytics -- you want to do anomaly detection
Hi Greg, thanks for the explanation! The example makes perfect sense to me,
I was under the impression that this was combining two independent fields
and I was wrong.
I'm not biased towards having or not a new field for it, but for
multi-value, don't we have a SortedSetDocValuesField that works
11 matches
Mail list logo
