mkhludnev commented on PR #2025:
URL: https://github.com/apache/solr/pull/2025#issuecomment-1842173386
Thanks @AndreyBozhko I'll check it next week
--
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
[
https://issues.apache.org/jira/browse/SOLR-16833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17793470#comment-17793470
]
Alessandro Benedetti commented on SOLR-16833:
-
I believe that it is a great i
dsmiley commented on code in PR #2118:
URL: https://github.com/apache/solr/pull/2118#discussion_r1416465264
##
solr/core/src/java/org/apache/solr/util/ThreadStats.java:
##
@@ -0,0 +1,94 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor
dsmiley commented on PR #2117:
URL: https://github.com/apache/solr/pull/2117#issuecomment-1841843687
You tagged me for review but really any cherry pick has already been
reviewed. If you are seeking my permission to put it into 9.4.1 -- I think we
use the list for that. Any bug fix is eli
dsmiley commented on PR #1221:
URL: https://github.com/apache/solr/pull/1221#issuecomment-1841829670
@heythm , for a very old PR, first get it up to date with main (merge main
into this) *then* update CHANGES.txt. Doing CHANGES.txt too early is no fun
merging. Also remember there is a bun
dsmiley commented on code in PR #1221:
URL: https://github.com/apache/solr/pull/1221#discussion_r1416431432
##
solr/CHANGES.txt:
##
@@ -160,7 +160,7 @@ Other Changes
SOLR-16575: splitshard should honour createNodeSet (noble)
-* SOLR-16577: Always log core load issues (Hayth
dsmiley commented on PR #2084:
URL: https://github.com/apache/solr/pull/2084#issuecomment-1841766856
By entering this CHANGES.txt into the 10.0 release section, it means you
believe it should not be back ported to 9x. Is that what you meant or was that
accidental? I'll move it and backpor
dsmiley commented on PR #2114:
URL: https://github.com/apache/solr/pull/2114#issuecomment-1841762567
Sorry; I wasn't paying enough attention. We shouldn't be using a
`SimpleOrderedMap` in any scenario where keys can be duplicated.
--
This is an automated message from the Apache Git Servi
[
https://issues.apache.org/jira/browse/SOLR-17057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley resolved SOLR-17057.
-
Fix Version/s: 9.4.1
Resolution: Fixed
> JSON Query regression; defType doesn't work in "p
thomascorthals commented on PR #2114:
URL: https://github.com/apache/solr/pull/2114#issuecomment-1841669328
> @thomascorthals, maybe a conversation for mailing list, but I'd love you
thoughts on if we generated a PHP library, would that make your life easier?
I had the same thought wh
[
https://issues.apache.org/jira/browse/SOLR-17057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17793437#comment-17793437
]
ASF subversion and git services commented on SOLR-17057:
Commit 7
brickpattern closed issue #662: /var/solr/data with incorrect ownership : Pod
not able to write
URL: https://github.com/apache/solr-operator/issues/662
--
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 t
dsmiley commented on PR #2114:
URL: https://github.com/apache/solr/pull/2114#issuecomment-1841636505
> I guess my point is that the actual API response, in JSON, is outputting
invalid JSON. That the fix is to change the way we handle multivalued fields to
nest them as an array under the top
epugh commented on PR #2114:
URL: https://github.com/apache/solr/pull/2114#issuecomment-1841603674
I guess my point is that the actual API response, in JSON, is outputting
invalid JSON. That the fix is to change the way we handle multivalued fields
to nest them as an array under the top le
dsmiley commented on PR #2114:
URL: https://github.com/apache/solr/pull/2114#issuecomment-1841596685
Remember `json.nl` parameter options, which exist to balance convenience of
the response with rigor over retrieving duplicated keys. But that only applies
to JSON.
https://solr.apache.or
AndreyBozhko commented on PR #2025:
URL: https://github.com/apache/solr/pull/2025#issuecomment-1841596601
Hi @HoustonPutman @mkhludnev - anything else to address for this PR? If not,
then it should be good to merge, but I don't have access to do so myself.
--
This is an automated message
dsmiley merged PR #2119:
URL: https://github.com/apache/solr/pull/2119
--
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
uvatbc commented on PR #2119:
URL: https://github.com/apache/solr/pull/2119#issuecomment-1841589697
> Notwistanding the one test that failed, are the results good to you
@uvatbc ?
Yes. The most important part was that the directory of execution was
`/crave-devspaces/pipeline/runs/710
dsmiley commented on PR #2119:
URL: https://github.com/apache/solr/pull/2119#issuecomment-1841566435
Notwistanding the one test that failed, are the results good to you @uvatbc ?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub
[
https://issues.apache.org/jira/browse/SOLR-17016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17793419#comment-17793419
]
ASF subversion and git services commented on SOLR-17016:
Commit 0
[
https://issues.apache.org/jira/browse/SOLR-17016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17793418#comment-17793418
]
ASF subversion and git services commented on SOLR-17016:
Commit 3
epugh merged PR #1988:
URL: https://github.com/apache/solr/pull/1988
--
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
mkhludnev commented on PR #2114:
URL: https://github.com/apache/solr/pull/2114#issuecomment-1841541673
I hardly get common hesitation over duplicated JSON keys. Why it is a
problem? Github come up with 480 json PHP parsers. Isn't there a library, which
don't feel so unique about keys?
-
[
https://issues.apache.org/jira/browse/SOLR-17068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17793413#comment-17793413
]
Eric Pugh commented on SOLR-17068:
--
FYI, going to merge https://github.com/apache/solr/p
uvatbc opened a new pull request, #2119:
URL: https://github.com/apache/solr/pull/2119
https://issues.apache.org/jira/browse/SOLR-X
# Description
The crave tests need to be run from the location of the clone, not the
default start directory.
# Solution
Change
epugh commented on code in PR #1988:
URL: https://github.com/apache/solr/pull/1988#discussion_r1416157539
##
solr/solr-ref-guide/modules/getting-started/pages/tutorial-vectors.adoc:
##
@@ -0,0 +1,172 @@
+= Exercise 5: Using Vectors
+:experimental:
+// Licensed to the Apache Soft
epugh commented on code in PR #1988:
URL: https://github.com/apache/solr/pull/1988#discussion_r1416153218
##
solr/solr-ref-guide/modules/getting-started/pages/tutorial-vectors.adoc:
##
@@ -0,0 +1,172 @@
+= Exercise 5: Using Vectors
+:experimental:
+// Licensed to the Apache Soft
janhoy commented on PR #2065:
URL: https://github.com/apache/solr/pull/2065#issuecomment-1841432832
Wdyt @risdenk ?
--
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 unsub
epugh commented on code in PR #1988:
URL: https://github.com/apache/solr/pull/1988#discussion_r1416144269
##
solr/solr-ref-guide/modules/getting-started/pages/tutorial-paramsets.adoc:
##
@@ -0,0 +1,147 @@
+= Exercise 4: Using ParamSets
+:experimental:
+// Licensed to the Apache
dsmiley commented on PR #2089:
URL: https://github.com/apache/solr/pull/2089#issuecomment-1841380317
On my mind here is wondering why we aren't simply calling `precommit` here?
Did we once have this but changed our minds (why?)
--
This is an automated message from the Apache Git Service.
epugh commented on code in PR #1988:
URL: https://github.com/apache/solr/pull/1988#discussion_r1416106801
##
solr/solr-ref-guide/modules/getting-started/pages/tutorial-paramsets.adoc:
##
@@ -0,0 +1,147 @@
+= Exercise 4: Using ParamSets
+:experimental:
+// Licensed to the Apache
epugh commented on PR #2114:
URL: https://github.com/apache/solr/pull/2114#issuecomment-1841348101
Okay, so I see that `cat` is duplicated because it's a multivalued field, so
we get:
```
"cat":{
"type":"string",
"schema":"I-S-UMOF-l",
"fl
epugh commented on PR #2114:
URL: https://github.com/apache/solr/pull/2114#issuecomment-1841341669
So... I think we are faced here with a different issue than how PHP is
handling the output When I run the curl command that was shared, I also
see the `cat` key come back mulitple times
epugh commented on PR #2114:
URL: https://github.com/apache/solr/pull/2114#issuecomment-1841339272
> A side: I recall some doubt as to whether Solr ought to even have a "php"
writer in the first place. Maybe it should be deprecated. Surely JSON is the
standard? WDYT CC @epugh
I think
[
https://issues.apache.org/jira/browse/SOLR-17096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17793360#comment-17793360
]
Paul McArthur commented on SOLR-17096:
--
I had considered making the plugin source pl
dsmiley merged PR #2112:
URL: https://github.com/apache/solr/pull/2112
--
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 #2112:
URL: https://github.com/apache/solr/pull/2112#issuecomment-1841197282
Finally; we're in much better shape. The build took 8m and the vast
majority of that was all in our build (Gradle etc.) which is under our control
to improve further; not doing "git clone"
HoustonPutman merged PR #16:
URL: https://github.com/apache/solr-docker/pull/16
--
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.
cclauss opened a new pull request, #16:
URL: https://github.com/apache/solr-docker/pull/16
(no comment)
--
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-ma
[
https://issues.apache.org/jira/browse/SOLR-17062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gerlowski resolved SOLR-17062.
Fix Version/s: 9.5
Assignee: Jason Gerlowski
Resolution: Fixed
After some b
[
https://issues.apache.org/jira/browse/SOLR-17062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17793337#comment-17793337
]
ASF subversion and git services commented on SOLR-17062:
Commit 6
[
https://issues.apache.org/jira/browse/SOLR-17077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1779#comment-1779
]
ASF subversion and git services commented on SOLR-17077:
Commit 5
dsmiley merged PR #2084:
URL: https://github.com/apache/solr/pull/2084
--
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
gbellaton opened a new pull request, #2118:
URL: https://github.com/apache/solr/pull/2118
https://issues.apache.org/jira/browse/SOLR-16986
# Description
This change logs cpuTime and localCpuTime in addition to QTime.
While QTime is the user time spend for a given request (dif
gerlowskija merged PR #1681:
URL: https://github.com/apache/solr/pull/1681
--
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-16835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17793326#comment-17793326
]
ASF subversion and git services commented on SOLR-16835:
Commit b
gerlowskija commented on code in PR #1681:
URL: https://github.com/apache/solr/pull/1681#discussion_r1415801779
##
solr/modules/ltr/example/README.md:
##
@@ -33,7 +33,15 @@ Please refer to the Solr Reference Guide's section on
[Learning To Rank](https:/
`ln -s /Users/YourN
psalagnac commented on PR #2084:
URL: https://github.com/apache/solr/pull/2084#issuecomment-1840992838
Thanks.
I added an entry in "Improvements", but not sure whether it should go to bug
"Bug Fixes". Maybe the code should have been like the from the beginning.
--
This is an automated
Jan Høydahl created SOLR-17097:
--
Summary: Upgrade to Lucene 9.9.0
Key: SOLR-17097
URL: https://issues.apache.org/jira/browse/SOLR-17097
Project: Solr
Issue Type: Improvement
Components
[
https://issues.apache.org/jira/browse/SOLR-17036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Roustant resolved SOLR-17036.
---
Fix Version/s: 9.5
Resolution: Fixed
> Lazy create VersionBucket in the update log to
[
https://issues.apache.org/jira/browse/SOLR-17036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17793305#comment-17793305
]
ASF subversion and git services commented on SOLR-17036:
Commit 5
dsmiley commented on PR #2084:
URL: https://github.com/apache/solr/pull/2084#issuecomment-1840901629
@psalagnac can you add a CHANGES.txt entry please? In "Other" or
"Improvements" depending on your point of view. Try to both be brief and
communicate the scope/impact -- kind of hard somet
janhoy commented on PR #2099:
URL: https://github.com/apache/solr/pull/2099#issuecomment-1840871615
I'm tempted to merge this to main, still as BadAlle, and see whether
[failure rate](http://fucit.org/solr-jenkins-reports/failure-report.html) comes
down from 42% during the coming days. I'm
janhoy commented on code in PR #2099:
URL: https://github.com/apache/solr/pull/2099#discussion_r1415674962
##
solr/modules/jwt-auth/src/test/org/apache/solr/security/jwt/JWTAuthPluginIntegrationTest.java:
##
@@ -116,6 +122,12 @@ public static void afterClass() throws Exception {
bruno-roustant merged PR #2021:
URL: https://github.com/apache/solr/pull/2021
--
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.ap
[
https://issues.apache.org/jira/browse/SOLR-17057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17793292#comment-17793292
]
ASF subversion and git services commented on SOLR-17057:
Commit 7
[
https://issues.apache.org/jira/browse/SOLR-17036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17793293#comment-17793293
]
ASF subversion and git services commented on SOLR-17036:
Commit 1
janhoy commented on PR #2065:
URL: https://github.com/apache/solr/pull/2065#issuecomment-1840794909
We should wait for 10.0.19 or explicitly exclude the bogous
`org.awaitility:awaitility` dependency (see
https://github.com/jetty/jetty.project/issues/10812)
--
This is an automated message
pareekdevanshu commented on issue #664:
URL: https://github.com/apache/solr-operator/issues/664#issuecomment-1840521689
we found the problem, SolrPrometheusExporter was using older version of Solr
image, we upgraded it to Solr version 8.11 and it fixed the problem.
--
This is an automated
pareekdevanshu closed issue #664: prometheus-exporter started throwing
different errors after upgrading solr operator to 0.7.0
URL: https://github.com/apache/solr-operator/issues/664
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHu
thomascorthals commented on PR #2114:
URL: https://github.com/apache/solr/pull/2114#issuecomment-1840475325
As someone on the PHP side of things, there's a good reason to look into
PHPS with the `/luke` handler in particular.
```shell
curl
'http://localhost:8983/solr/techproducts/
sigram merged PR #94:
URL: https://github.com/apache/solr-sandbox/pull/94
--
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
62 matches
Mail list logo
