marwin1991 commented on PR #3044:
URL: https://github.com/apache/solr/pull/3044#issuecomment-2601012956
@dsmiley Hello, check
https://github.com/logchange/logchange/issues/397#issuecomment-2601012870
--
This is an automated message from the Apache Git Service.
To respond to the message, p
[
https://issues.apache.org/jira/browse/SOLR-17562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17914461#comment-17914461
]
ASF subversion and git services commented on SOLR-17562:
Commit 0
malliaridis commented on PR #3044:
URL: https://github.com/apache/solr/pull/3044#issuecomment-2601045533
Marking the dependency to `groovy-all` as _provided_ at the plugin level
seems to be the best and easiest solution for solving this conflict. I am not
sure how we could apply constraints
[
https://issues.apache.org/jira/browse/SOLR-17619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated SOLR-17619:
--
Labels: pull-request-available (was: )
> Generate CHANGELOG.md (formerly CHANGES.txt) via logc
danielsason112 commented on issue #114:
URL: https://github.com/apache/solr-sandbox/issues/114#issuecomment-2601638032
Hey,
I came across this issue as well.
After triggering the encryption in a distributed SolrCloud, for a collection
with replication factor greater than 1, all fol