Dawid Weiss created LUCENE-10293:
Summary: Add an equivalent of ant's stage-maven-artifacts for the
release wizard
Key: LUCENE-10293
URL: https://issues.apache.org/jira/browse/LUCENE-10293
Project: Lu
Dawid Weiss created LUCENE-10294:
Summary: Avoid compiling javadocs twice in 'gradlew check'?
Key: LUCENE-10294
URL: https://issues.apache.org/jira/browse/LUCENE-10294
Project: Lucene - Core
[
https://issues.apache.org/jira/browse/LUCENE-10294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dawid Weiss updated LUCENE-10294:
-
Attachment: LUCENE-10294.patch
> Avoid compiling javadocs twice in 'gradlew check'?
> -
[
https://issues.apache.org/jira/browse/LUCENE-10294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17454471#comment-17454471
]
Uwe Schindler commented on LUCENE-10294:
+1 to only run "documentation" (site j
[
https://issues.apache.org/jira/browse/LUCENE-10294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17454475#comment-17454475
]
Uwe Schindler commented on LUCENE-10294:
bq. The downside is that a project-loc
[
https://issues.apache.org/jira/browse/LUCENE-10294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17454480#comment-17454480
]
Dawid Weiss commented on LUCENE-10294:
--
I thought about it but I don't know how to
[
https://issues.apache.org/jira/browse/LUCENE-10293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17454483#comment-17454483
]
Dawid Weiss commented on LUCENE-10293:
--
[~jpountz] - this PR has the task that ass
romseygeek commented on a change in pull request #521:
URL: https://github.com/apache/lucene/pull/521#discussion_r763792009
##
File path:
lucene/queries/src/java/org/apache/lucene/queries/intervals/Intervals.java
##
@@ -275,7 +275,10 @@ public static IntervalsSource ordered(In
dweiss commented on a change in pull request #521:
URL: https://github.com/apache/lucene/pull/521#discussion_r763795223
##
File path:
lucene/queries/src/java/org/apache/lucene/queries/intervals/Intervals.java
##
@@ -275,7 +275,10 @@ public static IntervalsSource ordered(Interv
romseygeek commented on pull request #521:
URL: https://github.com/apache/lucene/pull/521#issuecomment-987729638
This looks great, thanks @zhaih!
Could we also add a test for the atLeast case in TestIntervals? Testing in
highlighting is great, but I'd like to make sure we cover as mu
romseygeek commented on a change in pull request #521:
URL: https://github.com/apache/lucene/pull/521#discussion_r763805979
##
File path:
lucene/queries/src/java/org/apache/lucene/queries/intervals/Intervals.java
##
@@ -275,7 +275,10 @@ public static IntervalsSource ordered(In
ChrisHegarty commented on pull request #470:
URL: https://github.com/apache/lucene/pull/470#issuecomment-987783947
> I still have a gut feeling that if we defined explicit dependency
configurations for modules, they'd fit right in.
Yeah, I tend to agree. I also find the explicitness
jpountz opened a new pull request #524:
URL: https://github.com/apache/lucene/pull/524
The current `svn import` looks for docs where they used to be produced by the
`Ant` build, but `Gradle` now puts them in a different place.
--
This is an automated message from the Apache Git Ser
[
https://issues.apache.org/jira/browse/LUCENE-10287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17454574#comment-17454574
]
Dawid Weiss commented on LUCENE-10287:
--
I've added an integration layer test to th
jpountz commented on a change in pull request #523:
URL: https://github.com/apache/lucene/pull/523#discussion_r763869267
##
File path: lucene/distribution/build.gradle
##
@@ -126,3 +126,31 @@ tasks.matching {it.name in [
]}.all {
group "distribution"
}
+
+// Prepare a sona
[
https://issues.apache.org/jira/browse/LUCENE-10287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17454576#comment-17454576
]
Dawid Weiss commented on LUCENE-10287:
--
We could verify SPI sanity in a similar wa
dweiss commented on a change in pull request #523:
URL: https://github.com/apache/lucene/pull/523#discussion_r763876290
##
File path: lucene/distribution/build.gradle
##
@@ -126,3 +126,31 @@ tasks.matching {it.name in [
]}.all {
group "distribution"
}
+
+// Prepare a sonat
dweiss commented on a change in pull request #523:
URL: https://github.com/apache/lucene/pull/523#discussion_r763878796
##
File path: lucene/distribution/build.gradle
##
@@ -126,3 +126,31 @@ tasks.matching {it.name in [
]}.all {
group "distribution"
}
+
+// Prepare a sonat
dweiss commented on a change in pull request #523:
URL: https://github.com/apache/lucene/pull/523#discussion_r763878796
##
File path: lucene/distribution/build.gradle
##
@@ -126,3 +126,31 @@ tasks.matching {it.name in [
]}.all {
group "distribution"
}
+
+// Prepare a sonat
dweiss commented on a change in pull request #523:
URL: https://github.com/apache/lucene/pull/523#discussion_r763883614
##
File path: lucene/distribution/build.gradle
##
@@ -126,3 +126,31 @@ tasks.matching {it.name in [
]}.all {
group "distribution"
}
+
+// Prepare a sonat
Dawid Weiss created LUCENE-10295:
Summary: the release's .gitrev file is lost somewhere when
uploading release to the svn repository
Key: LUCENE-10295
URL: https://issues.apache.org/jira/browse/LUCENE-10295
[
https://issues.apache.org/jira/browse/LUCENE-10295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17454592#comment-17454592
]
Dawid Weiss commented on LUCENE-10295:
--
I think it's svn commands in the release w
jpountz opened a new pull request #525:
URL: https://github.com/apache/lucene/pull/525
It currently reads as Lucene is a full-text search library when it can do
much
more than that nowadays.
--
This is an automated message from the Apache Git Service.
To respond to the message, pl
[
https://issues.apache.org/jira/browse/LUCENE-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrien Grand resolved LUCENE-5590.
--
Resolution: Duplicate
> remove .zip binary artifacts
>
>
>
rmuir opened a new pull request #526:
URL: https://github.com/apache/lucene/pull/526
Looks like stray cats from back when it was shared with solr
--
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
madrob merged pull request #2624:
URL: https://github.com/apache/lucene-solr/pull/2624
--
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-unsu
chatman commented on pull request #2624:
URL: https://github.com/apache/lucene-solr/pull/2624#issuecomment-988062139
Why does it say there was a force push? Was it on apache/lucene-solr's
branch_8_11?
--
This is an automated message from the Apache Git Service.
To respond to the message,
[
https://issues.apache.org/jira/browse/LUCENE-10294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17454780#comment-17454780
]
Dawid Weiss commented on LUCENE-10294:
--
If there are no objections, I'll commit it
[
https://issues.apache.org/jira/browse/LUCENE-10294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17454783#comment-17454783
]
Uwe Schindler commented on LUCENE-10294:
Naaa, just the simple patch. All fine.
zhaih commented on a change in pull request #521:
URL: https://github.com/apache/lucene/pull/521#discussion_r764251721
##
File path:
lucene/queries/src/java/org/apache/lucene/queries/intervals/Intervals.java
##
@@ -275,7 +275,10 @@ public static IntervalsSource ordered(Interva
apanimesh061 commented on pull request #412:
URL: https://github.com/apache/lucene/pull/412#issuecomment-988169852
@dsmiley In order to make this portable to v9.x should we make 2 unit test
suites for "with builder" and "w/o builder"? It will just be easier to remove
the non-builder files
[
https://issues.apache.org/jira/browse/LUCENE-10294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17454795#comment-17454795
]
Robert Muir commented on LUCENE-10294:
--
+1, personally I only run {{check}} at the
dweiss commented on pull request #470:
URL: https://github.com/apache/lucene/pull/470#issuecomment-988215171
I went back to explicit configurations for modular dependencies. Maybe it
doesn't fit the gradle convention model but it's simpler and less magical in
the end (no automatic detectio
dweiss commented on pull request #470:
URL: https://github.com/apache/lucene/pull/470#issuecomment-988216299
Just to be clear: I don't want to convert all tests to be modular - the
other way around: I want existing tests to work as they currently do (in
classpath mode) but want to have the
zhaih commented on a change in pull request #521:
URL: https://github.com/apache/lucene/pull/521#discussion_r764406016
##
File path:
lucene/highlighter/src/test/org/apache/lucene/search/matchhighlight/TestMatchHighlighter.java
##
@@ -541,6 +539,234 @@ protected TokenStreamComp
zhaih commented on pull request #521:
URL: https://github.com/apache/lucene/pull/521#issuecomment-988304204
@romseygeek Sure thing, I added one more test for the atLeast change
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub
rmuir commented on pull request #470:
URL: https://github.com/apache/lucene/pull/470#issuecomment-988334834
> Just to be clear: I don't want to convert all tests to be modular - the
other way around: I want existing tests to work as they currently do (in
classpath mode) but want to have th
jtibshirani opened a new pull request #527:
URL: https://github.com/apache/lucene/pull/527
This exercises a challenging case where the documents to skip all happen to
be closest to the query vector. In many cases, HNSW appears to be robust to
this
case and maintains good recall.
[
https://issues.apache.org/jira/browse/LUCENE-10040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17454894#comment-17454894
]
Julie Tibshirani commented on LUCENE-10040:
---
I ran some local tests to sanity
rmuir merged pull request #526:
URL: https://github.com/apache/lucene/pull/526
--
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...@
rmuir merged pull request #513:
URL: https://github.com/apache/lucene/pull/513
--
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...@
[
https://issues.apache.org/jira/browse/LUCENE-10010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17454934#comment-17454934
]
ASF subversion and git services commented on LUCENE-10010:
--
Co
Robert Muir created LUCENE-10296:
Summary: Stop minimizing regexps
Key: LUCENE-10296
URL: https://issues.apache.org/jira/browse/LUCENE-10296
Project: Lucene - Core
Issue Type: Task
Affect
rmuir commented on pull request #225:
URL: https://github.com/apache/lucene/pull/225#issuecomment-988451392
ok, sorry, I realize the latest two PR-split-outs still don't solve your
problem. The API is still ugly because we still `minimize()` regexps, and that
implies `determinize()`... but
fmmoret commented on pull request #380:
URL: https://github.com/apache/lucene/pull/380#issuecomment-988465154
How far is this from making it into a release? We have been dealing with
this exact issue & have considered a local patch
--
This is an automated message from the Apache Git Ser
rmuir opened a new pull request #528:
URL: https://github.com/apache/lucene/pull/528
In current trunk, we let caller (e.g. RegExpQuery) try to "reduce" the
expression. The parser nor the low-level executors don't implicitly call
exponential-time algorithms anymore.
But now that we h
rmuir commented on pull request #225:
URL: https://github.com/apache/lucene/pull/225#issuecomment-988465898
ok one more, but I think it sets us up even better:
https://github.com/apache/lucene/pull/528
--
This is an automated message from the Apache Git Service.
To respond to the message
msokolov commented on a change in pull request #521:
URL: https://github.com/apache/lucene/pull/521#discussion_r764555865
##
File path:
lucene/queries/src/java/org/apache/lucene/queries/intervals/Intervals.java
##
@@ -275,7 +275,10 @@ public static IntervalsSource ordered(Inte
msokolov commented on a change in pull request #521:
URL: https://github.com/apache/lucene/pull/521#discussion_r764555865
##
File path:
lucene/queries/src/java/org/apache/lucene/queries/intervals/Intervals.java
##
@@ -275,7 +275,10 @@ public static IntervalsSource ordered(Inte
[
https://issues.apache.org/jira/browse/LUCENE-10040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17454967#comment-17454967
]
Xi Caoqiu commented on LUCENE-10040:
Weaviate have done similar method to implement
dweiss commented on pull request #470:
URL: https://github.com/apache/lucene/pull/470#issuecomment-988542101
The overlapping packages (tests accessing package-private classes) is the
main problem here, I think. Maybe there are workarounds to that - I'm a newbie
to all this myself, so still
zacharymorn commented on pull request #418:
URL: https://github.com/apache/lucene/pull/418#issuecomment-988548076
> These numbers are super interesting. Let's go with the approach of you
baseline for now since it performs better, sorry for putting you on a track
that performs worse. :)
52 matches
Mail list logo
