jpountz commented on issue #11770:
URL: https://github.com/apache/lucene/issues/11770#issuecomment-1247796727
> it seems that the core idea in this paper is similar to
IndexSortSortedNumericDocValuesRangeQuery
This is my understanding as well, though it says it uses the BKD tree to
f
jpountz merged PR #1068:
URL: https://github.com/apache/lucene/pull/1068
--
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.apach
shaie opened a new pull request, #11775:
URL: https://github.com/apache/lucene/pull/11775
### Description
Aside from some cleanups (typos, improving comments), this PR addresses few
issues:
1. `DirTaxoWriter.nextID` is declared `volatile` however this `nextID++` is
not a safe-
dweiss commented on PR #11774:
URL: https://github.com/apache/lucene/pull/11774#issuecomment-1247974260
Ah. missed the bull's eye, didn't I.
--
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 sp
rmuir commented on issue #11772:
URL: https://github.com/apache/lucene/issues/11772#issuecomment-1248043771
+1
--
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 unsubscrib
uschindler commented on issue #11772:
URL: https://github.com/apache/lucene/issues/11772#issuecomment-1248061894
Let's remove it. Actually the whole code is not tested at all. The removed
Testcase extends LuceneTestCase and not BaseDirectoryTestcase. The only thing
it does is to instantiate
dweiss merged PR #11774:
URL: https://github.com/apache/lucene/pull/11774
--
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
dweiss commented on issue #11772:
URL: https://github.com/apache/lucene/issues/11772#issuecomment-1248177490
Applied on 9x and main.
--
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 c
dweiss closed issue #11772: remove WindowsDirectory
URL: https://github.com/apache/lucene/issues/11772
--
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: i
uschindler commented on PR #11774:
URL: https://github.com/apache/lucene/pull/11774#issuecomment-1248218763
Thanks. I was just wondering, why this strange title of PR with "GH-"? I
would just put issue number in usual # notation. This does not highlight at all.
--
This is an automated mes
llermaly opened a new issue, #11776:
URL: https://github.com/apache/lucene/issues/11776
### Description
The following polygons are valid, but considered self intersecting by Lucene
:
```
POLYGON ((8.8970989818779 54.4134906575883, 8.90042774485873
54.4146874897743, 8.90594
jpountz commented on issue #11765:
URL: https://github.com/apache/lucene/issues/11765#issuecomment-1248281846
Lucene has a `QueryProfilerIndexSearcher` that allows to capture some of
this information for a given search, but it adds a lot of overhead. The way
that Lucene interleaves evaluati
jpountz closed issue #11765: Query optimizer statistics
URL: https://github.com/apache/lucene/issues/11765
--
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-mai
jpountz commented on issue #11761:
URL: https://github.com/apache/lucene/issues/11761#issuecomment-1248288919
Historically this was not configurable and Lucene would allow up to 50%
deleted documents. When we introduced an option, we made sure to introduce a
lower bound on the value because
LuXugang commented on issue #11770:
URL: https://github.com/apache/lucene/issues/11770#issuecomment-1248298615
> Could you tell me which lucene's files should I read, so I could implement
that algorithm?
I think you could first read `IndexSortSortedNumericDocValuesRangeQuery`,
then
mdmarshmallow commented on issue #11761:
URL: https://github.com/apache/lucene/issues/11761#issuecomment-1248348122
Hi, thanks for the response! Your explanation of 0% not being allowed makes
complete sense. For some context though, using our own forked version of
`TieredMergePolicy`, we ha
llermaly opened a new issue, #11777:
URL: https://github.com/apache/lucene/issues/11777
### Description
Some polygons are taking a lot of time to index (13MB, 15 minutes), and some
way larger ones (50MB+) taking just a couple of minutes.
Attached two of this polygons.
llermaly commented on issue #11767:
URL: https://github.com/apache/lucene/issues/11767#issuecomment-1248367379
Hi @iverase would be nice if you could go to
https://github.com/apache/lucene/issues/11777 and test with those polygons as
well. We are having Elastic Cloud timeouts because of the
nknize commented on issue #11767:
URL: https://github.com/apache/lucene/issues/11767#issuecomment-1248382179
> My proposal is to remove the method completely or at least not call this
method if the Tessellator has been called with the flag
`checkSelfIntersections` set to true.
>
> @n
patelprateek commented on issue #11765:
URL: https://github.com/apache/lucene/issues/11765#issuecomment-1248413173
@jpountz : After a query runs , i read that lucene uses filter cache where
it encodes the posting list using compressed bitmaps (roaring) , is there any
api to retrieve these c
llermaly commented on issue #11767:
URL: https://github.com/apache/lucene/issues/11767#issuecomment-1248415566
Here I have some valid polygons being rejected for self intersecting, in
case are useful for you to test:
https://github.com/apache/lucene/issues/11776
--
This is an auto
dweiss commented on PR #11774:
URL: https://github.com/apache/lucene/pull/11774#issuecomment-1248464122
This is an alternative notation for issue numbers that github actually
understands; see commit links, for example:
 and **ending**(어미) in
mecab-ko-dic.
(https://docs.google.com/spreadsheets/d/1-9blXKjtjeKZqsf4NzHeYJCrr49-nXeRF6D80udfcwY)
But
danmuzi opened a new pull request, #11779:
URL: https://github.com/apache/lucene/pull/11779
add detailed part-of-speech tag for particle and ending on nori.
The part-of-speech name was set based on the **Korean-English Learners'
Dictionary** of [National Institute of the Korean
Language]
janhoy commented on issue #10269:
URL: https://github.com/apache/lucene/issues/10269#issuecomment-1248570742
I'll close this old issue. Anyone discovering any new broken links on the
site can fix those in new PRs.
--
This is an automated message from the Apache Git Service.
To respond to
janhoy closed issue #10269: Lucene web site broken links [LUCENE-9229]
URL: https://github.com/apache/lucene/issues/10269
--
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 uns
janhoy commented on PR #591:
URL: https://github.com/apache/lucene/pull/591#issuecomment-1248760591
@msokolov This has been hanging for a while, and I'll now merge it into main
and then to branch_9x.
Just though I'd alert you as 9.4.0 RM, although I don't anticipate any
issues with
iverase commented on issue #11767:
URL: https://github.com/apache/lucene/issues/11767#issuecomment-1248975086
>The method was originally introduced to postpone self intersection removal
I don't understand this. We re claiming in the java docs that polygons
should not be self-intersec
nknize commented on issue #11767:
URL: https://github.com/apache/lucene/issues/11767#issuecomment-124898
> I don't understand this. We re claiming in the java docs that polygons
should not be self-intersecting and we do not introduce self-intersections in
our code, why we want to remove
30 matches
Mail list logo
