romseygeek commented on issue #10247:
URL: https://github.com/apache/lucene/issues/10247#issuecomment-1436600828
The scoring is sufficiently different with intervals that I don't think
that's really viable.
--
This is an automated message from the Apache Git Service.
To respond to the mes
iverase opened a new issue, #12161:
URL: https://github.com/apache/lucene/issues/12161
Similar to https://github.com/apache/lucene/issues/11199, it would be nice
to have a class that can index both LatLonPoint and LatLonDocValues.
--
This is an automated message from the Apache Git Servic
iverase opened a new pull request, #12162:
URL: https://github.com/apache/lucene/pull/12162
Add new field that index both LatLonPoint and LatLonDocValues and provides
factory methods for the operations that can be performed. Those are:
```
Query newGeometryQuery(String field, Shape
ioanatia commented on issue #11829:
URL: https://github.com/apache/lucene/issues/11829#issuecomment-1436865949
@jpountz unless there have been more occurrences after
https://github.com/apache/lucene/pull/12124 was merged, could this issue be
closed?
--
This is an automated message from t
mkhludnev commented on issue #10247:
URL: https://github.com/apache/lucene/issues/10247#issuecomment-1436936304
Thanks for answer, @romseygeek. Could you elaborate? Do you mean spans'
scoring is equal to disjunction of phrases and intervals scoring can't be
tweaked somehow closer to it? Ho
rmuir commented on PR #12162:
URL: https://github.com/apache/lucene/pull/12162#issuecomment-1437062026
Can we add newPolygonQuery and newBoxQuery just like LatLonPoint already has?
To me, the newGeometryQuery method is unusable and overcomplicated. No user
should struggle with how to
rmuir commented on PR #12162:
URL: https://github.com/apache/lucene/pull/12162#issuecomment-1437065088
I would also suggest removing the newGeometryQuery() method from what should
be an easy-to-use field. The api is too insane...
--
This is an automated message from the Apache Git Service
rmuir commented on PR #12162:
URL: https://github.com/apache/lucene/pull/12162#issuecomment-1437079826
in short: just the combination of methods from LatLonPoint +
LatLonDocValuesField, minus the useless and overcomplicated geometry one, that
provides no real benefits to point data:
iverase commented on PR #12162:
URL: https://github.com/apache/lucene/pull/12162#issuecomment-1437092325
Sorry but I totally disagree, this is the most typical API for a geo
application so if someone else struggle with it then it should not be
developing a geo application.
Anyway I don'
rmuir commented on PR #12162:
URL: https://github.com/apache/lucene/pull/12162#issuecomment-1437097724
LOL, dude who do you think wrote the point-in-polygon, distance, box stuff
here? I guess i "should not be developing a geo application"
What use-case does this crappy newGeometryQuer
rmuir commented on PR #12162:
URL: https://github.com/apache/lucene/pull/12162#issuecomment-1437100061
and yeah, to be clear i'm -1 against this change until we address this. I
also have serious concerns about anyone who thinks this newGeometryQuery is
"the most typical API". Stop, breathe,
rmuir commented on PR #12162:
URL: https://github.com/apache/lucene/pull/12162#issuecomment-1437105265
also btw, this API should not exist to support "people developing geo
applications" anyway. I could give two shits about "geo nerds".
These point method apis exist to support normal
iverase commented on PR #12162:
URL: https://github.com/apache/lucene/pull/12162#issuecomment-1437106462
-1 for removing it so here we are.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the spe
rmuir commented on PR #12162:
URL: https://github.com/apache/lucene/pull/12162#issuecomment-1437106577
and don't forget, newGeometryQuery doesn't "do anything" you cant already do
with the simple methods anyway for poinut data. It is 100% useless
--
This is an automated message from the A
rmuir commented on PR #12162:
URL: https://github.com/apache/lucene/pull/12162#issuecomment-1437108733
-1 for removing a method that does nothing and has no value? :)
Dude you have lost your mind! I recommend a psychiatrist!
--
This is an automated message from the Apache Git Servi
iverase commented on PR #12162:
URL: https://github.com/apache/lucene/pull/12162#issuecomment-1437192476
LOL it is impossible to disagree with you and not get insulted
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use th
benwtrent commented on code in PR #12152:
URL: https://github.com/apache/lucene/pull/12152#discussion_r1112285170
##
lucene/core/src/test/org/apache/lucene/search/TestDocAndScoreQuery.java:
##
@@ -0,0 +1,94 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or
dnhatn opened a new pull request, #12163:
URL: https://github.com/apache/lucene/pull/12163
Backport of #12147 to 9x
This change adjusts the cache policy to ensure that all segments in the max
tier to be cached. Before, we cache segments that have more than 3% of the
total documents
dnhatn opened a new pull request, #12164:
URL: https://github.com/apache/lucene/pull/12164
Backport of #12147 to 9_5
This change adjusts the cache policy to ensure that all segments in the max
tier to be cached. Before, we cache segments that have more than 3% of the
total documents
dnhatn merged PR #12163:
URL: https://github.com/apache/lucene/pull/12163
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@lucene.apac
dnhatn merged PR #12164:
URL: https://github.com/apache/lucene/pull/12164
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@lucene.apac
MarcusSorealheis commented on PR #12162:
URL: https://github.com/apache/lucene/pull/12162#issuecomment-1437925210
I've been doing some research and hope MongoDB can help make an impact here
soon for all of our customers. However, not speaking for MongoDB and only for
myself, I want to weigh
MarcusSorealheis commented on PR #12162:
URL: https://github.com/apache/lucene/pull/12162#issuecomment-1437977171
At this point, I don't know how a feature like Spatial knn could be
implemented and it certainly would not rely on doc values for the approximation
query, the existing and propo
23 matches
Mail list logo
