[
https://issues.apache.org/jira/browse/SOLR-16591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17802414#comment-17802414
]
David Smiley commented on SOLR-16591:
-
Maybe that is why. In deprecating it, I don't
dsmiley commented on code in PR #2172:
URL: https://github.com/apache/solr/pull/2172#discussion_r1441384176
##
solr/server/etc/security.policy:
##
@@ -219,6 +219,9 @@ grant {
permission java.io.FilePermission "${solr.allowPaths}",
"read,write,delete,readlink";
permission
dsmiley commented on PR #2126:
URL: https://github.com/apache/solr/pull/2126#issuecomment-1876136104
Agreed that 9.5 should not be released without reconciling the two
approaches.
I think I would prefer to revert SOLR-17079 as it exists today, then merge
this PR SOLR-17096 (after wha
janhoy opened a new pull request, #674:
URL: https://github.com/apache/solr-operator/pull/674
Fixes #673
DRAFT, code largely generated by GitHub copilot, just throwing up the idea
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on t
janhoy opened a new issue, #673:
URL: https://github.com/apache/solr-operator/issues/673
To reproduce:
1. Create a cluster with ingress enabled (e.g. `solrAddressability.external:
Ingress`)
2. Update the spec by removing the external addressability
3. Both `Ingress` resource and
janhoy commented on issue #667:
URL: https://github.com/apache/solr-operator/issues/667#issuecomment-1875935157
Had the same need. Perhaps a configurable service-name template would be
cool, where the default could be `serviceNameTemplate: %n-%r-solrcloud` given
that %n=namespace, %r=releas
janhoy merged PR #2135:
URL: https://github.com/apache/solr/pull/2135
--
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
pvcnt commented on PR #2126:
URL: https://github.com/apache/solr/pull/2126#issuecomment-1875808589
I don't know when Solr 9.5 is going to be released, but IMHO we should make
sure that it is not released with two different ways of configuring a cluster
plugin in solr.xml, or even not releas
janhoy commented on code in PR #2172:
URL: https://github.com/apache/solr/pull/2172#discussion_r1440772945
##
solr/server/etc/security.policy:
##
@@ -219,6 +219,9 @@ grant {
permission java.io.FilePermission "${solr.allowPaths}",
"read,write,delete,readlink";
permission j
pjmcarthur commented on PR #2126:
URL: https://github.com/apache/solr/pull/2126#issuecomment-1875774998
@pvcnt @dsmiley I think there should be a follow-up PR that addresses the
replica placement plugin. My understanding is that from a user's perspective,
the configuration of solr.xml wrt.
tflobbe commented on code in PR #2172:
URL: https://github.com/apache/solr/pull/2172#discussion_r1440641745
##
solr/server/etc/security.policy:
##
@@ -219,6 +219,9 @@ grant {
permission java.io.FilePermission "${solr.allowPaths}",
"read,write,delete,readlink";
permission
Märt created SOLR-17110:
---
Summary: unquoted uuid values in json query response
Key: SOLR-17110
URL: https://issues.apache.org/jira/browse/SOLR-17110
Project: Solr
Issue Type: Bug
Security Level:
epugh commented on code in PR #2173:
URL: https://github.com/apache/solr/pull/2173#discussion_r1440574155
##
solr/core/src/java/org/apache/solr/handler/IndexFetcher.java:
##
@@ -332,24 +336,26 @@ private void setLeaderUrl(String leaderUrl) {
solrCore
.getCo
aaronsuns commented on issue #671:
URL: https://github.com/apache/solr-operator/issues/671#issuecomment-1875441585
Here is the quick hack to add those container securityContext
```
diff --git a/controllers/util/solr_util.go b/controllers/util/solr_util.go
index 0c7f098..47fde76 10064
sgowda97 opened a new issue, #672:
URL: https://github.com/apache/solr-operator/issues/672
Hi,
I am running solr-operator 0.8.0, solr 9.4.0 on GKE. Here is my YAML file
`
apiVersion: solr.apache.org/v1beta1
kind: SolrCloud
metadata:
name: dev
spec:
solrAddr
[
https://issues.apache.org/jira/browse/SOLR-16203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Høydahl reassigned SOLR-16203:
--
Assignee: Jan Høydahl
> Using SPI lookups of analysis components results in factories that don
janhoy commented on PR #2175:
URL: https://github.com/apache/solr/pull/2175#issuecomment-1875084210
Second attempt:
The first attempt did not work for packages, since
`FieldTypePluginLoader#init` was too early in the cycle to initialize analyzers
from packages.
Managed schema
janhoy commented on PR #2175:
URL: https://github.com/apache/solr/pull/2175#issuecomment-1875068088
First attempt in efadf94dc6ac87027ef708c71c58d3848e7a9a0d:
Naïve solution, explicitly calling `inform()` in `FieldTypePluginLoader`.
The two tests from JIRA are added to this PR to demo
aaronsuns commented on issue #489:
URL: https://github.com/apache/solr-operator/issues/489#issuecomment-1875059878
Any news on this one?
--
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 specif
aaronsuns commented on issue #671:
URL: https://github.com/apache/solr-operator/issues/671#issuecomment-1875044226
It looks like related with this issue:
https://github.com/apache/solr-operator/issues/489
--
This is an automated message from the Apache Git Service.
To respond to the
20 matches
Mail list logo
