epugh opened a new pull request, #2261:
URL: https://github.com/apache/solr/pull/2261
https://issues.apache.org/jira/browse/SOLR-17017
# Description
Please provide a short description of the changes you're making with this
pull request.
# Solution
[
https://issues.apache.org/jira/browse/SOLR-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17817183#comment-17817183
]
James Dyer commented on SOLR-599:
-
See PR [#2259|https://github.com/apache/solr/pull/2259],
dsmiley merged PR #2189:
URL: https://github.com/apache/solr/pull/2189
--
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...@solr.apache.or
dsmiley commented on PR #2256:
URL: https://github.com/apache/solr/pull/2256#issuecomment-1942791182
Thanks Clay. I've removed the foiled attempt at removing "solr-root" again.
But I had done so earlier in this PR's history and at no point has this PR
published a build scan. Yes I'm awar
dsmiley opened a new pull request, #2260:
URL: https://github.com/apache/solr/pull/2260
Plugins can be disabled via `enable="false"` but unfortunately it's up to
the caller of creating a PluginInfo to remember to consult this flag. This PR
addresses plugin disablement in solr.xml stuff. N
janhoy commented on issue #686:
URL: https://github.com/apache/solr-operator/issues/686#issuecomment-1942732253
Zk operator is not a hard req. I recommend disabling it and instead run a zk
ensemble with bitnami’s zk helm chart which also has more up to date zk images.
--
This is an automa
janhoy commented on PR #2259:
URL: https://github.com/apache/solr/pull/2259#issuecomment-1942728149
This is so cool! Let’s make it the new default client in a solrj-core
artifact?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitH
dsmiley commented on code in PR #2244:
URL: https://github.com/apache/solr/pull/2244#discussion_r1488505233
##
solr/core/src/java/org/apache/solr/search/QueryLimits.java:
##
@@ -41,11 +43,15 @@ private QueryLimits() {}
* statement will hinge on hasXXXLimit() static method at
mmoscher commented on issue #686:
URL: https://github.com/apache/solr-operator/issues/686#issuecomment-1942415528
@fliphess yes ya totally right. We're running the zookeeper-operator as well.
Just double-checked our local deployment. Colima spawns - when running with
k3s - an aarch64
[
https://issues.apache.org/jira/browse/SOLR-17106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17817128#comment-17817128
]
Aparna Suresh commented on SOLR-17106:
--
Thanks for the feedback! Sorry I did not hav
clayburn commented on PR #2256:
URL: https://github.com/apache/solr/pull/2256#issuecomment-1942292686
If you are wanting your project to show as `solr` instead of `solr-root`,
you should instead set the `rootProject.name` in your `gradle.properties` file
to `solr`. Setting a project id in t
schotten opened a new issue, #687:
URL: https://github.com/apache/solr-operator/issues/687
I use the Helm, and, i can't found the options to configure the
recurrence/schedule in the helm. I can only configure the repository
 throws IOExce
cpoerschke opened a new pull request, #2258:
URL: https://github.com/apache/solr/pull/2258
Subjective of course, but I think more `final` use would help with code
reading/comprehension. Noticed whilst looking at #2248 changes to this method.
No JIRA ticket or CHANGES.txt entry needed IMHO.
cpoerschke commented on code in PR #2248:
URL: https://github.com/apache/solr/pull/2248#discussion_r1488340137
##
solr/core/src/java/org/apache/solr/search/SolrMultiCollectorManager.java:
##
@@ -0,0 +1,150 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or
cpoerschke commented on code in PR #2248:
URL: https://github.com/apache/solr/pull/2248#discussion_r1488240645
##
solr/solr-ref-guide/modules/indexing-guide/examples/stemdict.txt:
##
Review Comment:
> Looks like you removed a symlink?
Restored in
https://github.com/
janhoy merged PR #18:
URL: https://github.com/apache/solr-docker/pull/18
--
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...@solr.apache.
risdenk commented on PR #1999:
URL: https://github.com/apache/solr/pull/1999#issuecomment-1941952643
@cpoerschke https://github.com/apache/solr/pull/1510 might be helpful here.
I have a few wip prs for newer jdks
--
This is an automated message from the Apache Git Service.
To respond to t
murblanc commented on code in PR #2207:
URL: https://github.com/apache/solr/pull/2207#discussion_r1486781194
##
solr/core/src/java/org/apache/solr/update/UpdateHandler.java:
##
@@ -116,10 +116,13 @@ public UpdateHandler(SolrCore core, UpdateLog updateLog) {
parseEventListen
cpoerschke commented on PR #1999:
URL: https://github.com/apache/solr/pull/1999#issuecomment-1941906981
> ... It would be interesting to think about if there was a way for Solr
`main` branch to somehow depend on the Lucene `main` branch release that jumps
the minimum Java versions all aroun
cpoerschke commented on code in PR #1999:
URL: https://github.com/apache/solr/pull/1999#discussion_r1488136630
##
versions.props:
##
@@ -49,6 +49,7 @@ org.apache.httpcomponents:httpmime=4.5.14
org.apache.kerby:*=1.0.1
org.apache.logging.log4j:*=2.21.0
org.apache.lucene:*=9.9.
HoustonPutman commented on PR #18:
URL: https://github.com/apache/solr-docker/pull/18#issuecomment-1941859267
> Hey, well, I'm sorry to bother you here as my question would be out of
this topic. I'm wondering why `9.4.1`, `9.5`, `9.5.0`, `9.5.0-slim` don't
support arm64, but `9` and `latest
[
https://issues.apache.org/jira/browse/SOLR-17066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17817029#comment-17817029
]
ASF subversion and git services commented on SOLR-17066:
Commit 6
ozlerhakan commented on PR #18:
URL: https://github.com/apache/solr-docker/pull/18#issuecomment-1941646531
Hey, well, I'm sorry to bother you here as my question would be out of this
topic. I'm wondering why `9.4.1`, `9.5`, `9.5.0`, `9.5.0-slim` don't support
arm64, but `9` and `latest` do?
[
https://issues.apache.org/jira/browse/SOLR-17066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17817014#comment-17817014
]
ASF subversion and git services commented on SOLR-17066:
Commit b
gerlowskija merged PR #2255:
URL: https://github.com/apache/solr/pull/2255
--
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...@solr.apach
[
https://issues.apache.org/jira/browse/SOLR-17023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Pugh updated SOLR-17023:
-
Fix Version/s: main (10.0)
> Use Modern NLP Models from Apache OpenNLP with Solr
> --
epugh commented on PR #1999:
URL: https://github.com/apache/solr/pull/1999#issuecomment-1941576718
Lucene 9 requires older version of Java than the minimum required version
that OpenNLP requires. That means that this PR is pending a release of Lucene
10, and the adoption of Lucene 10 by Sol
[
https://issues.apache.org/jira/browse/SOLR-17148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Pugh resolved SOLR-17148.
--
Fix Version/s: 9.6.0
Resolution: Fixed
Thanks [~duttsanjay] for this nice fix!
> Config API lie
[
https://issues.apache.org/jira/browse/SOLR-17148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17817006#comment-17817006
]
ASF subversion and git services commented on SOLR-17148:
Commit 3
[
https://issues.apache.org/jira/browse/SOLR-17148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17817005#comment-17817005
]
ASF subversion and git services commented on SOLR-17148:
Commit a
epugh merged PR #2247:
URL: https://github.com/apache/solr/pull/2247
--
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...@solr.apache.org
[
https://issues.apache.org/jira/browse/SOLR-17145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17817001#comment-17817001
]
ASF subversion and git services commented on SOLR-17145:
Commit 8
[
https://issues.apache.org/jira/browse/SOLR-17145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17816998#comment-17816998
]
ASF subversion and git services commented on SOLR-17145:
Commit c
gerlowskija merged PR #2252:
URL: https://github.com/apache/solr/pull/2252
--
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...@solr.apach
fliphess commented on issue #686:
URL: https://github.com/apache/solr-operator/issues/686#issuecomment-1941436821
@mmoscher We run on arm64 graviton machines on AWS and the default
zookeeper-operator image shipped with it, does not support running on graviton
for us. It does on m1/m2/m3 bec
mmoscher commented on issue #686:
URL: https://github.com/apache/solr-operator/issues/686#issuecomment-1940840764
Hi @fliphess,
what issue do face in particular?
We've currently 5 developers on Mac M1 or M2 (arm64) using colima for local
development and they are able to use the so
37 matches
Mail list logo
