Re: [PR] SOLR-17105, SOLR-17366: Require a location for local backups [solr]
github-actions[bot] closed pull request #2161: SOLR-17105, SOLR-17366: Require a location for local backups URL: https://github.com/apache/solr/pull/2161 -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
Re: [PR] Parses CHANGES.txt to identify contributors [solr]
github-actions[bot] commented on PR #2424: URL: https://github.com/apache/solr/pull/2424#issuecomment-2466515099 This PR has had no activity for 60 days and is now labeled as stale. Any new activity will remove the stale label. To attract more reviewers, please tag people who might be familiar with the code area and/or notify the d...@solr.apache.org mailing list. To exempt this PR from being marked as stale, make it a draft PR or add the label "exempt-stale". If left unattended, this PR will be closed after another 60 days of inactivity. Thank you for your contribution! -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
Re: [PR] SOLR-17105, SOLR-17366: Require a location for local backups [solr]
github-actions[bot] commented on PR #2161: URL: https://github.com/apache/solr/pull/2161#issuecomment-2466515105 This PR is now closed due to 60 days of inactivity after being marked as stale. Re-opening this PR is still possible, in which case it will be marked as active again. -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
Re: [PR] SOLR-17353: Fix for golang version 1.18 [solr]
github-actions[bot] closed pull request #2542: SOLR-17353: Fix for golang version 1.18 URL: https://github.com/apache/solr/pull/2542 -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
Re: [PR] SOLR-17353: Fix for golang version 1.18 [solr]
github-actions[bot] commented on PR #2542: URL: https://github.com/apache/solr/pull/2542#issuecomment-2466515081 This PR is now closed due to 60 days of inactivity after being marked as stale. Re-opening this PR is still possible, in which case it will be marked as active again. -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
Re: [PR] SOLR-17483: Backport cleanup zk-related logic in bin/solr.cmd [solr]
epugh commented on PR #2823: URL: https://github.com/apache/solr/pull/2823#issuecomment-2466186163 I just saw a bug report (with a patch!) reported to the dev list: https://issues.apache.org/jira/browse/SOLR-17551. Looking a bit closer, I wonder if we apply this PR to branch_9x and branch_9_7, then does this fix the reported bug as well, or if we only do the bug fix in branch_9_7, and leave this one to go to branch_9x? -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Commented] (SOLR-17551) zk upconfig command broken on Windows
[
https://issues.apache.org/jira/browse/SOLR-17551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17896884#comment-17896884
]
Eric Pugh commented on SOLR-17551:
--
We have this other PR, [https://github.com/apache/solr/pull/2823] that
[~malliaridis] put together that also (I think) deals with this issue by
simplifying our code paths. I am a bit on the fence on which way to go! Do
the bigger refacotring, and ship in 9.7.1, or just this specific fix?
> zk upconfig command broken on Windows
> -
>
> Key: SOLR-17551
> URL: https://issues.apache.org/jira/browse/SOLR-17551
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
>Affects Versions: 9.7
> Environment: Windows Server 2022, Windows 10
>Reporter: Mingchun Zhao
>Priority: Critical
> Attachments: SOLR-17551.patch
>
>
> When running the `solr zk upconfig` command on Windows, the following error
> occurs.
> {code:java}
> C:\Program Files\solr-9.7.0\bin>solr zk upconfig -d sitecore_configs -n
> sitecoreconfigset -z 10.1.0.11:2181,10.1.0.12:2181,10.1.0.13:2181
> 'ELSE' is not recognized as an internal or external command,
> operable program or batch file.
> Failed to parse command-line arguments due to: Unrecognized option: --zk-host
> ZK_HOSTusage: bin/solr upconfig -d -n [-url ] [-z
> ]List of options:
> -d,--conf-dir Local directory with configs.
> -n,--conf-name Configset name in ZooKeeper.
> -url,--solr-url Base Solr URL, which can be used to determine the
> zk-host if that's not known; defaults to:
> http://Solrcloud-test-Solr01:8983.
> -z,--zk-host Zookeeper connection string; unnecessary if ZK_HOST
> is defined in solr.in.sh; otherwise,
> defaults to localhost:9983.Please see the Reference
> Guide for more tools documentation:
> https://solr.apache.org/guide/solr/latest/deployment-guide/solr-control-script-reference.html
> WARN - 2024-11-07 11:29:32.428; org.apache.solr.common.cloud.SolrZkClient;
> Using default ZkCredentialsInjector. ZkCredentialsInjector is not secure, it
> creates an empty list of credentials which leads to 'OPEN_ACL_UNSAFE' ACLs to
> Zookeeper nodes
> WARN - 2024-11-07 11:29:33.666; org.apache.solr.common.cloud.SolrZkClient;
> Using default ZkACLProvider. DefaultZkACLProvider is not secure, it creates
> 'OPEN_ACL_UNSAFE' ACLs to Zookeeper nodes
> Uploading C:\Program
> Files\solr-9.7.0\server\solr\configsets\sitecore_configs\conf for config
> sitecoreconfigset to ZooKeeper at 10.1.0.11:2181 {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Commented] (SOLR-11646) Ref Guide: Update API examples to include v2 style examples
[ https://issues.apache.org/jira/browse/SOLR-11646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17896885#comment-17896885 ] Eric Pugh commented on SOLR-11646: -- I'm curious if we think we could close this ticket as done? Any place that doesn't have a v2 at this point I would consider a "bug" and a surprise, as I think we've gone through everything! > Ref Guide: Update API examples to include v2 style examples > --- > > Key: SOLR-11646 > URL: https://issues.apache.org/jira/browse/SOLR-11646 > Project: Solr > Issue Type: Improvement > Components: documentation, v2 API >Reporter: Cassandra Targett >Assignee: Cassandra Targett >Priority: Major > Labels: V2 > Time Spent: 9h > Remaining Estimate: 0h > > The Ref Guide currently only has a single page with what might be generously > called an overview of the v2 API added in 6.5 > (https://lucene.apache.org/solr/guide/v2-api.html) but most of the actual > APIs that support the v2 approach do not show an example of using it with the > v2 style. A few v2-style APIs are already used as examples, but there's > nothing consistent. > With this issue I'll add API input/output examples throughout the Guide. Just > in terms of process, my intention is to have a series of commits to the pages > as I work through them so we make incremental progress. I'll start by adding > a list of pages/APIs to this issue so the scope of the work is clear. > Once this is done we can figure out what to do with the V2 API page itself - > perhaps it gets archived and replaced with another page that describes Solr's > APIs overall; perhaps by then we figure out something else to do with it. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Commented] (SOLR-11441) windows shell splits args on "=" so we should consider updating our docs to always quote args like -Dfoo=bar or improve bin/solr.cmd to account for this
[
https://issues.apache.org/jira/browse/SOLR-11441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17896893#comment-17896893
]
Eric Pugh commented on SOLR-11441:
--
Is this still an issue? I find it hard to believe that this obvious of an
issue still exists!
> windows shell splits args on "=" so we should consider updating our docs to
> always quote args like -Dfoo=bar or improve bin/solr.cmd to account for this
>
>
> Key: SOLR-11441
> URL: https://issues.apache.org/jira/browse/SOLR-11441
> Project: Solr
> Issue Type: Bug
> Components: documentation, scripts and tools
> Environment: Windows 10, possible other versions as well (presumably
> not when running cygwin?)
>Reporter: Chris M. Hostetter
>Priority: Major
> Attachments: SOLR-11441.patch
>
>
> confusing exchange with a user on freenode#solr led to this discovery...
> {noformat}
> 14:07 < sara_:#solr> New question: bin/solr start -e techproducts
> -Dsolr.ltr.enabled=true
> 14:07 < sara_:#solr> gave me invalid command-line option:true
> 14:07 < sara_:#solr> anyone knows why?
> ...
> 15:02 < sara_:#solr> i have 6.6.1 @elyograg
> 15:03 < sara_:#solr> mine is a windows 10 machine
> ...
> 15:28 < sara_:#solr> @elyograg i just downloaded solr-7.0.0 and ran bin/solr
> start -e techproducts -Dsolr.ltr.enabled=true
> 15:28 < sara_:#solr> it still gave me invalid command-line
> ...
> 15:29 <@hoss:#solr> sara_: the only thing i can think of is that windows 10
> is splitting your command line on '=' ? ... can you try
> quoting the entire command line arg so the script gets
> the entire -Dsolr.ltr.enabled=true ? (not sure how to quote
> strings in the windows command shell -- i would assume
> "-Dsolr.ltr.enabled=true"
> 15:32 <@hoss:#solr> sigh ... yes, aparently windows things "=" is a shell
> delimiter: https://ss64.com/nt/syntax-esc.html
> 15:33 <@hoss:#solr> s/shell delimiter/parameter delimiter in shell commands/
> 15:33 < sara_:#solr> you are genius!
> 15:34 < sara_:#solr> you and elyograg. you guys are fantastic. Saving me from
> looking at the cmd script or shell script
> 15:34 <@hoss:#solr> sara_: do i have your permission to copy/paste this
> exchange into our bug tracker as a note about updating our docs
> (and maybe making the solr.cmd smart enough to handle
> this) ?
> 15:45 < sara_:#solr> sure of course
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Commented] (SOLR-17483) bin/solr.cmd run_zk method can be drastically simplified
[ https://issues.apache.org/jira/browse/SOLR-17483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17896902#comment-17896902 ] ASF subversion and git services commented on SOLR-17483: Commit 9023e70ff72e4a2b08277469e980b4ed7bc2cd56 in solr's branch refs/heads/branch_9x from Christos Malliaridis [ https://gitbox.apache.org/repos/asf?p=solr.git;h=9023e70ff72 ] SOLR-17483: Backport cleanup zk-related logic in bin/solr.cmd (#2823) * SOLR-17484: Cleanup zk-related logic in bin/solr.cmd (#2816) * Remove ZK logic from solr.cmd as it is obsolete * Fix unreachable auth tool in solr.cmd * Fix invalid references (cherry picked from commit c2091d0258400c9064b8c67fe0d974e367ecccfd) * Fix exec issue when executing bin\solr.cmd start The closing parentheses caused the IF to be closed before the echo message was fully printed, leading to "mode." being executed instead of printed. > bin/solr.cmd run_zk method can be drastically simplified > > > Key: SOLR-17483 > URL: https://issues.apache.org/jira/browse/SOLR-17483 > Project: Solr > Issue Type: Sub-task > Components: cli >Affects Versions: 9.8 >Reporter: Eric Pugh >Assignee: Christos Malliaridis >Priority: Minor > Labels: pull-request-available > Time Spent: 2h > Remaining Estimate: 0h > > In the bin/solr.cmd windows script, the :run_zk method still has all the > logic for validating arguments. However, we can now rely on the java code > for that. > I suspect there are other opportunities for shrinking bin/solr.cmd as well > now that argument parsing/handling is in Java. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Commented] (SOLR-17484) Prometheus Exporter should efficiently work without ZK dependency
[ https://issues.apache.org/jira/browse/SOLR-17484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17896903#comment-17896903 ] ASF subversion and git services commented on SOLR-17484: Commit 9023e70ff72e4a2b08277469e980b4ed7bc2cd56 in solr's branch refs/heads/branch_9x from Christos Malliaridis [ https://gitbox.apache.org/repos/asf?p=solr.git;h=9023e70ff72 ] SOLR-17483: Backport cleanup zk-related logic in bin/solr.cmd (#2823) * SOLR-17484: Cleanup zk-related logic in bin/solr.cmd (#2816) * Remove ZK logic from solr.cmd as it is obsolete * Fix unreachable auth tool in solr.cmd * Fix invalid references (cherry picked from commit c2091d0258400c9064b8c67fe0d974e367ecccfd) * Fix exec issue when executing bin\solr.cmd start The closing parentheses caused the IF to be closed before the echo message was fully printed, leading to "mode." being executed instead of printed. > Prometheus Exporter should efficiently work without ZK dependency > - > > Key: SOLR-17484 > URL: https://issues.apache.org/jira/browse/SOLR-17484 > Project: Solr > Issue Type: Improvement > Components: contrib - prometheus-exporter >Reporter: David Smiley >Priority: Major > > The Prometheus Exporter, when pointing at SolrCloud, CloudSolrClient with a > ZK connecting backing it. This issue proposes switching it to the Solr/HTTP > based ClusterState provider. > Note there are some performance issues with calls it makes to > CloudSolrClient.getClusterState which shifts from a simple getter to a remote > call that returns the entire cluster state. Perhaps out of scope or a > dependency? -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
Re: [PR] SOLR-17483: Backport cleanup zk-related logic in bin/solr.cmd [solr]
malliaridis commented on PR #2823: URL: https://github.com/apache/solr/pull/2823#issuecomment-2466207109 I've further looked into backporting this, but it would break compatibility to other deprecated commands, which we probably don't want to mess with again. I would therefore apply the patch from https://issues.apache.org/jira/browse/SOLR-17551 instead. -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Resolved] (SOLR-8242) contrib/analytics: relocate hasDocValues() check out of FieldFacetAccumulator
[
https://issues.apache.org/jira/browse/SOLR-8242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Pugh resolved SOLR-8242.
-
Resolution: Won't Fix
analytics contrib was removed in the past.
> contrib/analytics: relocate hasDocValues() check out of FieldFacetAccumulator
> -
>
> Key: SOLR-8242
> URL: https://issues.apache.org/jira/browse/SOLR-8242
> Project: Solr
> Issue Type: Task
>Reporter: Christine Poerschke
>Priority: Minor
>
> from SOLR-8147:
> [~cpoerschke] wrote:
> bq. Considering the overall class usage and calling chains, might the
> {{hasDocValues()}} check be relocated to somewhere higher up? From a cursory
> look {{AnalyticsContentHandler.endElement}} and
> {{AnalyticsRequestFactory.(parse|makeFieldFacet|setFieldFacetParam)}}
> construct {{FieldFacetRequest}} objects and perhaps the hasDocValues check
> could happen there i.e. catch the invalid input/bad request when considering
> request parameters and then within the lower level accumulator object the
> hasDocValues check goes away and no SolrException need be thrown by the
> {{FieldFacetAccumulator}}.
> [~houstonputman] wrote:
> bq. I agree that the {{hasDocValues()}} check should be moved to
> {{AnalyticsRequestFactory.(makeFieldFacet|setFieldFacetParam)}}. It shouldn't
> add any complexity since those methods are where the {{SchemaField}}
> references, which {{FieldFacetAccumulator}} uses, originate. Other error
> checking could be done in a similar manner. For example {{result()}} calls in
> query and range facets could be validated after
> {{AnalyticsRequestFactory.parse()}} is finished, this would greatly reduce
> the complexity in the {{(BasicAccumulator|FacetingAccumulator).getResult()}}
> and {{FacetingAccumulator.getQueryResult()}} methods. There are probably
> others, but that's the first that popped into my head.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Commented] (SOLR-4444) Developer Curb Appeal: doc: Explaining Production vs. Dev environment, Java Memory, etc.
[ https://issues.apache.org/jira/browse/SOLR-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17896913#comment-17896913 ] Eric Pugh commented on SOLR-: - If I ever get my "development.yml" and "production.yml" default configurations idea in SOLR-7871 done, that would take care of a lot of this! > Developer Curb Appeal: doc: Explaining Production vs. Dev environment, Java > Memory, etc. > > > Key: SOLR- > URL: https://issues.apache.org/jira/browse/SOLR- > Project: Solr > Issue Type: Improvement > Components: SolrCloud >Affects Versions: 4.1 >Reporter: Mark Bennett >Priority: Major > Fix For: 4.9, 6.0 > > > Issues: > Which things are OK for prod, which are not. For example, if we ever do > "schemaless", why it might not be good in prod. > Locking down REST API access > Sizing, RAM, disk (and type of disk) > JVM memory advice, Xms, Xmx, physical memory, Java 6 vs. Java 7 > Where to turn logging on and off > How much to obsess about schema.xml settings > Memory hot spots: sorting, facets, etc > Using external vs. embedded ZooKeeper > Well known addresses and syntax for ZK nodes > Caching, etc. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Commented] (SOLR-13571) Make recent RefGuide rank well in Google
[
https://issues.apache.org/jira/browse/SOLR-13571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17896915#comment-17896915
]
Eric Pugh commented on SOLR-13571:
--
I don't know if this is just "time heals all wounds" since the last comment,
but I tried a variety of queries related to Solr using an anonymous browser,
and the "latest" showed up at the top predominantly. Yes, 6.6 did some up
furthur down, (and some others) but mostly the latest.
I thought about loading into Quepid a bunch of queries and doing a custom
server end point for google, and rating docs, but that seemed over kill ;).
Please reopen if you think this is still an issue.
> Make recent RefGuide rank well in Google
>
>
> Key: SOLR-13571
> URL: https://issues.apache.org/jira/browse/SOLR-13571
> Project: Solr
> Issue Type: Improvement
> Components: documentation
>Reporter: Jan Høydahl
>Priority: Major
>
> Spinoff from SOLR-13548
> The old Confluence ref-guide has a lot of pages pointing to it, and all of
> that link karma is delegated to the {{/solr/guide/6_6/}} html ref guide,
> making it often rank top. However we'd want newer content to rank high. See
> these comments for some first ideas.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Resolved] (SOLR-13571) Make recent RefGuide rank well in Google
[
https://issues.apache.org/jira/browse/SOLR-13571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Pugh resolved SOLR-13571.
--
Resolution: Fixed
> Make recent RefGuide rank well in Google
>
>
> Key: SOLR-13571
> URL: https://issues.apache.org/jira/browse/SOLR-13571
> Project: Solr
> Issue Type: Improvement
> Components: documentation
>Reporter: Jan Høydahl
>Priority: Major
>
> Spinoff from SOLR-13548
> The old Confluence ref-guide has a lot of pages pointing to it, and all of
> that link karma is delegated to the {{/solr/guide/6_6/}} html ref guide,
> making it often rank top. However we'd want newer content to rank high. See
> these comments for some first ideas.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Commented] (SOLR-10998) Support "Accept" request header as alternative to "wt" parameter
[
https://issues.apache.org/jira/browse/SOLR-10998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17896912#comment-17896912
]
Eric Pugh commented on SOLR-10998:
--
We recently removed the language specific wt like python, ruby, and php, so
that at least simplifies what is needed in this ticket.
> Support "Accept" request header as alternative to "wt" parameter
>
>
> Key: SOLR-10998
> URL: https://issues.apache.org/jira/browse/SOLR-10998
> Project: Solr
> Issue Type: Improvement
> Components: Server
>Reporter: Jan Høydahl
>Priority: Major
> Labels: http-headers, standards
>
> Spinoff from
> [email|https://lists.apache.org/thread.html/b4ec90b01bc075a98947e77b0a683308f760221dccb11be5819d1601@%3Cdev.lucene.apache.org%3E]
> Advertises which content types, expressed as MIME types, the client is able
> to understand
> [https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Accept]
> Could replace or at least be an alternative to “wt”. Examples:
> Accept: application/xml
> Accept: text/csv
> Issue: Most browsers sends a long accept header, typically
> application/xml,text/html, {{\*/\*}} , and now that json is default for Solr,
> we’d need to serve JSON if the accept header includes “\*/\*"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Commented] (SOLR-12540) Solr API - standardize parameter names to either camel case or dot-separated lowercase
[ https://issues.apache.org/jira/browse/SOLR-12540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17896911#comment-17896911 ] Eric Pugh commented on SOLR-12540: -- [~gerlowskija] in the V2 work, don't we have this somewhat better handled? We have explicit "dev docs" for this, and I'm thinking that we could potentially close this Jira as "fixed in the V2 apis"??? > Solr API - standardize parameter names to either camel case or dot-separated > lowercase > -- > > Key: SOLR-12540 > URL: https://issues.apache.org/jira/browse/SOLR-12540 > Project: Solr > Issue Type: Task >Affects Versions: 7.4 >Reporter: Shawn Heisey >Priority: Major > > Parameter names for the Solr API are a mixture of camel case and > dot-separated notation. Here's an API that uses both notations: > https://lucene.apache.org/solr/guide/7_4/collections-api.html#create-parameters > That API even has parameters that use both forms at the same time: > createNodeSet.shuffle and collection.configName are examples. > We need to standardize on one notation, simplify the names where possible, > and deprecate non-conforming parameters. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
Re: [PR] SOLR-17483: Backport cleanup zk-related logic in bin/solr.cmd [solr]
epugh commented on PR #2823: URL: https://github.com/apache/solr/pull/2823#issuecomment-2466238477 > I've further looked into backporting this, but it would break compatibility to other deprecated commands, which we probably don't want to mess with again. I would therefore apply the patch from https://issues.apache.org/jira/browse/SOLR-17551 instead. Awesome.Could I talk you into applying it? I don't have a windows box and it's tricky enough I don't want to break things worse. Thanks for making a decision on which way to go -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
Re: [PR] SOLR-17533: Rearrange and cleanup solr.cmd [solr]
epugh commented on code in PR #2822: URL: https://github.com/apache/solr/pull/2822#discussion_r1835408541 ## solr/bin/solr.cmd: ## @@ -383,18 +355,19 @@ goto done @echo. goto done - -REM Really basic command-line arg parsing +REM Parse arguments for special commands (start, stop, restart) Review Comment: Yeah, it does.. I think the way in `bin/solr` it is that first you do everything. Then you do auth. Then you do the remaining ones of start, stop, restart. -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
Re: [PR] SOLR-14680: Remove SimpleMap (affects NamedList) [solr]
epugh commented on PR #2856: URL: https://github.com/apache/solr/pull/2856#issuecomment-2466240086 I don't think I have the knowledge to weigh in here, but I did like that this removes 10x more lines than it adds! -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Commented] (SOLR-10329) Rebuild Solr examples
[ https://issues.apache.org/jira/browse/SOLR-10329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17896886#comment-17896886 ] Eric Pugh commented on SOLR-10329: -- Talked about this at this years Community over Code with folks and there seemed to be agreement that this is needed. Introduce some NEW examples that are more minimal and representative of some use cases. For example, an ecommerce one that sets similiarity to 1 and is more attibute oriented. A new "multilingual" one. A new "document" search oriented one with lots of vectors. > Rebuild Solr examples > - > > Key: SOLR-10329 > URL: https://issues.apache.org/jira/browse/SOLR-10329 > Project: Solr > Issue Type: Wish > Components: examples >Reporter: Alexandre Rafalovitch >Priority: Major > Labels: gsoc2017 > > Apache Solr ships with a number of examples. They evolved from a kitchen sync > example and are rather large. When new Solr features are added, they are > often shoehorned into the most appropriate example and sometimes are not > represented at all. > Often, for new users, it is hard to tell what part of example is relevant, > what part is default and what part is demonstrating something completely > different. > It would take significant (and very appreciated) effort to review all the > examples and rebuild them to provide clean way to showcase best practices > around base and most recent features. > Specific issues are around kitchen sync vs. minimal examples, better approach > to "schemaless" mode and creating examples and datasets that allow to create > both "hello world" and more-advanced tutorials. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Assigned] (SOLR-10095) Examples do not respect SOLR_HOME and SOLR_LOGS_DIR
[
https://issues.apache.org/jira/browse/SOLR-10095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Pugh reassigned SOLR-10095:
Assignee: Eric Pugh
> Examples do not respect SOLR_HOME and SOLR_LOGS_DIR
> ---
>
> Key: SOLR-10095
> URL: https://issues.apache.org/jira/browse/SOLR-10095
> Project: Solr
> Issue Type: Bug
> Components: scripts and tools
>Reporter: Jan Høydahl
>Assignee: Eric Pugh
>Priority: Minor
>
> The examples do not respect {{SOLR_HOME}} or {{SOLR_LOGS_DIR}} env, but
> always try to write index and logs to {{SOLR_HOME/../logs}}. Problem is when
> Solr is installed using the installer script, then {{/opt/solr}} is not
> supposed to be writable, and starting the examples fail.
> h3. Reproduce
> {noformat}
> sudo install_solr_service.sh solr-6.4.0.tgz
> sudo su solr
> export SOLR_INCLUDE="/etc/default/solr.in.sh"
> /opt/solr/bin/solr -e dih
> Starting up Solr on port 8983 using command:
> /opt/solr/bin/solr start -p 8983 -s "/opt/solr/example/example-DIH/solr"
> Exception in thread "main" java.nio.file.AccessDeniedException:
> /opt/solr/example/example-DIH/solr/../logs
> at
> sun.nio.fs.UnixException.translateToIOException(UnixException.java:84)
> at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
> at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
> at
> sun.nio.fs.UnixFileSystemProvider.createDirectory(UnixFileSystemProvider.java:384)
> at java.nio.file.Files.createDirectory(Files.java:674)
> at java.nio.file.Files.createAndCheckIsDirectory(Files.java:781)
> at java.nio.file.Files.createDirectories(Files.java:767)
> at
> org.apache.solr.util.SolrCLI$UtilsTool.archiveGcLogs(SolrCLI.java:3604)
> at org.apache.solr.util.SolrCLI$UtilsTool.runTool(SolrCLI.java:3587)
> at org.apache.solr.util.SolrCLI.main(SolrCLI.java:256)
> Failed archiving old GC logs
> Exception in thread "main" java.nio.file.AccessDeniedException:
> /opt/solr/example/example-DIH/solr/../logs
> at
> sun.nio.fs.UnixException.translateToIOException(UnixException.java:84)
> at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
> at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
> at
> sun.nio.fs.UnixFileSystemProvider.createDirectory(UnixFileSystemProvider.java:384)
> at java.nio.file.Files.createDirectory(Files.java:674)
> at java.nio.file.Files.createAndCheckIsDirectory(Files.java:781)
> at java.nio.file.Files.createDirectories(Files.java:767)
> at
> org.apache.solr.util.SolrCLI$UtilsTool.archiveConsoleLogs(SolrCLI.java:3633)
> at org.apache.solr.util.SolrCLI$UtilsTool.runTool(SolrCLI.java:3590)
> at org.apache.solr.util.SolrCLI.main(SolrCLI.java:256)
> Failed archiving old console logs
> ERROR: Logs directory /opt/solr/example/example-DIH/solr/../logs could not be
> created. Exiting
> ERROR: Process exited with an error: 1 (Exit value: 1)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Commented] (SOLR-6934) bin/solr -e cloud has poor failure behavior when solr has (certain types of) startup errors
[
https://issues.apache.org/jira/browse/SOLR-6934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17896894#comment-17896894
]
Eric Pugh commented on SOLR-6934:
-
We have the various bin/solr assert commands that could be used here, plus the
AssertTool.java has static methods that could be used.
Is this a ticket [~hossman] that we still feel is valid? If you wrote a more
specific "DO this at this point" type statement, I'd be happy to work on it.
I just need a bit more direction...
> bin/solr -e cloud has poor failure behavior when solr has (certain types of)
> startup errors
> ---
>
> Key: SOLR-6934
> URL: https://issues.apache.org/jira/browse/SOLR-6934
> Project: Solr
> Issue Type: Bug
>Reporter: Chris M. Hostetter
>Priority: Major
>
> Earlier today, sarowe backported a jetty config change that broke 5x because
> it refered to a jetty feature that only existed in jetty9 (5x still using
> jetty8).
> Ass a result, jetty started up and was listenting on the specified port - but
> the solr webapp code never loaded.
> this caused an interesting failure behavior in bin/solr...
> {noformat}
> hossman@frisbee:~/lucene/5x_dev/solr$ bin/solr -e cloud -noprompt
> Welcome to the SolrCloud example!
> Starting up 2 Solr nodes for your example SolrCloud cluster.
> Creating Solr home directory
> /home/hossman/lucene/5x_dev/solr/example/cloud/node1/solr
> Cloning Solr home directory
> /home/hossman/lucene/5x_dev/solr/example/cloud/node1 into
> /home/hossman/lucene/5x_dev/solr/example/cloud/node2
> Starting up SolrCloud node1 on port 8983 using command:
> solr start -cloud -s
> /home/hossman/lucene/5x_dev/solr/example/cloud/node1/solr -p 8983
> Waiting to see Solr listening on port 8983 [/]
> Started Solr server on port 8983 (pid=29954). Happy searching!
>
> Starting node2 on port 7574 using command:
> solr start -cloud -s
> /home/hossman/lucene/5x_dev/solr/example/cloud/node2/solr -p 7574 -z
> localhost:9983
> Waiting to see Solr listening on port 7574 [/]
> Started Solr server on port 7574 (pid=30099). Happy searching!
> Exception in thread "main" org.noggit.JSONParser$ParseException: JSON Parse
> Error: char=<,position=0 BEFORE='<' AFTER='html> http-equiv="Content-'
> at org.noggit.JSONParser.err(JSONParser.java:356)
> at org.noggit.JSONParser.handleNonDoubleQuoteString(JSONParser.java:712)
> at org.noggit.JSONParser.next(JSONParser.java:886)
> at org.noggit.JSONParser.nextEvent(JSONParser.java:930)
> at org.noggit.ObjectBuilder.(ObjectBuilder.java:44)
> at org.noggit.ObjectBuilder.getVal(ObjectBuilder.java:37)
> at
> org.apache.solr.util.SolrCLI$SolrResponseHandler.handleResponse(SolrCLI.java:447)
> at
> org.apache.solr.util.SolrCLI$SolrResponseHandler.handleResponse(SolrCLI.java:443)
> at
> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:218)
> at
> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:160)
> at
> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:136)
> at org.apache.solr.util.SolrCLI.getJson(SolrCLI.java:469)
> at org.apache.solr.util.SolrCLI.getJson(SolrCLI.java:422)
> at
> org.apache.solr.util.SolrCLI$CreateCollectionTool.runTool(SolrCLI.java:1081)
> at org.apache.solr.util.SolrCLI.main(SolrCLI.java:195)
> SolrCloud example running, please visit http://localhost:8983/solr
> {noformat}
> we should make bin/solr a little smarter in failure cases like this --
> perhaps the "Waiting to see Solr listening on port 7574" check should be more
> aggressive, and actually verify that something like /admin/cores returns 200
> and a parsable JSON response?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Resolved] (SOLR-16592) films tutorial should be documented in Ref Guide
[ https://issues.apache.org/jira/browse/SOLR-16592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Pugh resolved SOLR-16592. -- Resolution: Implemented This was done some point in the past! > films tutorial should be documented in Ref Guide > > > Key: SOLR-16592 > URL: https://issues.apache.org/jira/browse/SOLR-16592 > Project: Solr > Issue Type: Improvement > Components: documentation >Affects Versions: 9.0 >Reporter: Eric Pugh >Priority: Minor > > The /solr/examples/films/README.md has grown to be a full on tutorial, > including a new patch in SOLR-16574. > When you do bin/solr start -help you get a reference to the examples, but no > pointer to tutorials in ref guide... maybe add. Also examples/README.md > refers basically the same page in two ways.. "For a Solr tutorial" should > really be "For a list of different tutorials related to various Solr projects > like Docker and Solr-Operator or something better. > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Resolved] (SOLR-17) XSD for solr requests/responses
[ https://issues.apache.org/jira/browse/SOLR-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Pugh resolved SOLR-17. --- Resolution: Abandoned We've embraced the OpenAPI specification for describing our APIs, and we're making good progress on using them in our "V2" apis. I'm closing this ticket in favour of our Open API efforts. > XSD for solr requests/responses > --- > > Key: SOLR-17 > URL: https://issues.apache.org/jira/browse/SOLR-17 > Project: Solr > Issue Type: Improvement >Reporter: Mike Baranczak >Priority: Minor > Attachments: SOLR-17.Mattmann.121709.patch.txt, > UselessRequestHandler.java, solr-complex.xml, solr-rev2.xsd, solr.xsd > > > Attaching an XML schema definition for the responses and the update requests. > I needed to do this for myself anyway, so I might as well contribute it to > the project. > At the moment, I have no plans to write an XSD for the config documents, but > it wouldn't be a bad idea. > TODO: change the schema URL. I'm guessing that Apache already has some sort > of naming convention for these? -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
Re: [PR] SOLR-17483: Backport cleanup zk-related logic in bin/solr.cmd [solr]
malliaridis merged PR #2823: URL: https://github.com/apache/solr/pull/2823 -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
[PR] SOLR-17352: CLI - Remove unsupported options for auth command [solr]
malliaridis opened a new pull request, #2858: URL: https://github.com/apache/solr/pull/2858 https://issues.apache.org/jira/browse/SOLR-17352 # Description The auth command is currently using `-s` for setting `solr-home` (bin\solr.cmd) and for `solr-url` (AuthTool). This overlapping prevents the user from using the `-s` option for `solr-url`. # Solution Remove overlapping and deprecated option variants (`-s` and `-d`) from `bin/solr.cmd` to allow `-s` being used for `solr-url`. Changes should be backported to `branch_9x` (not sure if `branch_9_7` should also include these changes). # Tests Tested manually only due to the lack of windows tests. See [SOLR-17508](https://issues.apache.org/jira/browse/SOLR-17508). # Checklist Please review the following and check all that apply: - [X] I have reviewed the guidelines for [How to Contribute](https://github.com/apache/solr/blob/main/CONTRIBUTING.md) and my code conforms to the standards described there to the best of my ability. - [ ] I have created a Jira issue and added the issue ID to my pull request title. - [X] I have given Solr maintainers [access](https://help.github.com/en/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork) to contribute to my PR branch. (optional but recommended, not available for branches on forks living under an organisation) - [X] I have developed this patch against the `main` branch. - [X] I have run `./gradlew check`. - [ ] I have added tests for my changes. - [ ] I have added documentation for the [Reference Guide](https://github.com/apache/solr/tree/main/solr/solr-ref-guide) -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Updated] (SOLR-5103) Plugin Improvements (packaging, loading, distribution)
[ https://issues.apache.org/jira/browse/SOLR-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Smiley updated SOLR-5103: --- Summary: Plugin Improvements (packaging, loading, distribution) (was: Plugin Improvements) > Plugin Improvements (packaging, loading, distribution) > -- > > Key: SOLR-5103 > URL: https://issues.apache.org/jira/browse/SOLR-5103 > Project: Solr > Issue Type: Improvement > Components: Plugin system >Reporter: Grant Ingersoll >Assignee: Grant Ingersoll >Priority: Major > Fix For: 7.0 > > > We should make it easier to add plugins by defining a plugin package, ala a > Hadoop Job jar, which is a self--contained archive of a plugin that can be > easily installed (even from the UI!) and configured programmatically. > This serves as an umbrella issue, see sub tasks and linked issues. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Resolved] (SOLR-14464) Loading data in solr from Neo4j Database
[
https://issues.apache.org/jira/browse/SOLR-14464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley resolved SOLR-14464.
-
Resolution: Invalid
Appears this should be a user/dev list thread to get help. Only create a
ticket for a specific finding.
> Loading data in solr from Neo4j Database
>
>
> Key: SOLR-14464
> URL: https://issues.apache.org/jira/browse/SOLR-14464
> Project: Solr
> Issue Type: Task
> Components: query
>Affects Versions: 7.5
>Reporter: Narayana
>Priority: Major
> Attachments: Solr Log Error.docx, neo4j-data-config.xml,
> solrconfig.xml
>
>
> Hi Team, I have my Neo4j Data setup by loading/importing the data from .cvs
> file. Now I am trying to move the Neo4j data to my solr database. So in my
> solr database configuration file when trying to connect to my Neo4j giving
> necessary credentials it is not working .
> My local : Necessary parameters provided in solr
> name=employee
> neo4j-hostname=bolt://localhost:7687
> neo4j-username=neo4j
> neo4j-password=**
> solr.data.dir=C:\\Users\\.\\MySolr\\solr-7.5.0\\solr-7.5.0\\server\solr\\data
>
>
> Attached is the Query String present in neo4j-data-config.xml
>
> After executing the import query - getting the following error that can be
> seen in : solr Log Error.
>
> My finding was - there is a unicode character getting added up -
> {{}} It is Unicode zero-width space which seems to be generated when
> forwarding the Querystring.
>
> Even tried adding this in xml beginning: " encoding="utf-8"?>" And ""
> Both didn't work.
>
> Please let me know if any more details are still required.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Commented] (SOLR-17484) Prometheus Exporter should efficiently work without ZK dependency
[ https://issues.apache.org/jira/browse/SOLR-17484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17896935#comment-17896935 ] Christos Malliaridis commented on SOLR-17484: - Not again 😣 I used the cherrypick.sh, which enters vim for the commit message in case of a conflict, and once I try to save and quit like in nano, the shortcuts I use increment the number the cursor is current at. This tool is too powerful for me. 😑 It should be SOLR-17483 for anyone reading this. :( > Prometheus Exporter should efficiently work without ZK dependency > - > > Key: SOLR-17484 > URL: https://issues.apache.org/jira/browse/SOLR-17484 > Project: Solr > Issue Type: Improvement > Components: contrib - prometheus-exporter >Reporter: David Smiley >Priority: Major > > The Prometheus Exporter, when pointing at SolrCloud, CloudSolrClient with a > ZK connecting backing it. This issue proposes switching it to the Solr/HTTP > based ClusterState provider. > Note there are some performance issues with calls it makes to > CloudSolrClient.getClusterState which shifts from a simple getter to a remote > call that returns the entire cluster state. Perhaps out of scope or a > dependency? -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
Re: [PR] SOLR-17483: Backport cleanup zk-related logic in bin/solr.cmd [solr]
malliaridis commented on PR #2823: URL: https://github.com/apache/solr/pull/2823#issuecomment-2466306295 Leaving this as a note: Mistakenly changed the commit message with vim during cherrypick. The correct issue is SOLR-17483, not SOLR-17484. -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Commented] (SOLR-17551) zk upconfig command broken on Windows
[
https://issues.apache.org/jira/browse/SOLR-17551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17896879#comment-17896879
]
Eric Pugh commented on SOLR-17551:
--
Thank you for filing this bug report, and even better, attaching a patch file!
I am going to convert this to a PR so we can look at it.
The first change seems to make total sense, however i am less clear on the
second change. I will try and elaborate in the PR.
We will have a 9.7.1 very soon.
> zk upconfig command broken on Windows
> -
>
> Key: SOLR-17551
> URL: https://issues.apache.org/jira/browse/SOLR-17551
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
>Affects Versions: 9.7
> Environment: Windows Server 2022, Windows 10
>Reporter: Mingchun Zhao
>Priority: Critical
> Attachments: SOLR-17551.patch
>
>
> When running the `solr zk upconfig` command on Windows, the following error
> occurs.
> {code:java}
> C:\Program Files\solr-9.7.0\bin>solr zk upconfig -d sitecore_configs -n
> sitecoreconfigset -z 10.1.0.11:2181,10.1.0.12:2181,10.1.0.13:2181
> 'ELSE' is not recognized as an internal or external command,
> operable program or batch file.
> Failed to parse command-line arguments due to: Unrecognized option: --zk-host
> ZK_HOSTusage: bin/solr upconfig -d -n [-url ] [-z
> ]List of options:
> -d,--conf-dir Local directory with configs.
> -n,--conf-name Configset name in ZooKeeper.
> -url,--solr-url Base Solr URL, which can be used to determine the
> zk-host if that's not known; defaults to:
> http://Solrcloud-test-Solr01:8983.
> -z,--zk-host Zookeeper connection string; unnecessary if ZK_HOST
> is defined in solr.in.sh; otherwise,
> defaults to localhost:9983.Please see the Reference
> Guide for more tools documentation:
> https://solr.apache.org/guide/solr/latest/deployment-guide/solr-control-script-reference.html
> WARN - 2024-11-07 11:29:32.428; org.apache.solr.common.cloud.SolrZkClient;
> Using default ZkCredentialsInjector. ZkCredentialsInjector is not secure, it
> creates an empty list of credentials which leads to 'OPEN_ACL_UNSAFE' ACLs to
> Zookeeper nodes
> WARN - 2024-11-07 11:29:33.666; org.apache.solr.common.cloud.SolrZkClient;
> Using default ZkACLProvider. DefaultZkACLProvider is not secure, it creates
> 'OPEN_ACL_UNSAFE' ACLs to Zookeeper nodes
> Uploading C:\Program
> Files\solr-9.7.0\server\solr\configsets\sitecore_configs\conf for config
> sitecoreconfigset to ZooKeeper at 10.1.0.11:2181 {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Resolved] (SOLR-7099) bin/solr -cloud mode should launch a local ZK in its own process using zkcli's runzk option (instead of embedded in the first Solr process)
[ https://issues.apache.org/jira/browse/SOLR-7099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Pugh resolved SOLR-7099. - Resolution: Not A Problem I'm going to close this because we are explicitly going in the direction of leveraging embedded ZK for small clusters. See https://issues.apache.org/jira/browse/SOLR-17492 for some new proposed documentation for the Ref Guide on a more opinonated scaling up of Solr strategies. > bin/solr -cloud mode should launch a local ZK in its own process using > zkcli's runzk option (instead of embedded in the first Solr process) > --- > > Key: SOLR-7099 > URL: https://issues.apache.org/jira/browse/SOLR-7099 > Project: Solr > Issue Type: Improvement > Components: scripts and tools, SolrCloud >Reporter: Timothy Potter >Priority: Major > > Embedded ZK is great for unit testing and quick examples, but as soon as > someone wants to restart their cluster, embedded mode causes a lot of issues, > esp. if you restart the node that embeds ZK. Of course we don't want users to > have to install ZooKeeper just to get started with Solr either. > Thankfully, ZkCLI already includes a way to launch ZooKeeper in its own > process but still within the Solr directory structure. We can hide the > details and complexity of working with ZK in the bin/solr script. The > solution to this should still make it very clear that this is for getting > started / examples and not to be used in production. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Commented] (SOLR-14193) Update tutorial.adoc(line no:664) so that command executes in windows enviroment
[
https://issues.apache.org/jira/browse/SOLR-14193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17896897#comment-17896897
]
Eric Pugh commented on SOLR-14193:
--
[~balaji-s] i'm following up after we made a lot of improvements to the Solr
CLI. The post tool is now part of the Solr command: bin/solr post and I'm
curious if this issue remains?
If so, I'd love to tweak the ref guide to have a unix version and a windows
version. Or otherwise figure out how to deal with the | character.
> Update tutorial.adoc(line no:664) so that command executes in windows
> enviroment
>
>
> Key: SOLR-14193
> URL: https://issues.apache.org/jira/browse/SOLR-14193
> Project: Solr
> Issue Type: Bug
> Components: documentation
>Affects Versions: 8.4
>Reporter: balaji sundaram
>Priority: Minor
> Attachments: solr-tutorial.adoc
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
>
> {{When executing the following command in windows 10 "java -jar -Dc=films
> -Dparams=f.genre.split=true&f.directed_by.split=true&f.genre.separator=|&f.directed_by.separator=|
> -Dauto example\exampledocs\post.jar example\films\*.csv", it throws error "&
> was unexpected at this time."}}
> Fix: the command should escape "&" and "|" symbol{{}}
> {{}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Commented] (SOLR-16124) Solr Example should prompt for ZK port
[
https://issues.apache.org/jira/browse/SOLR-16124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17896887#comment-17896887
]
Eric Pugh commented on SOLR-16124:
--
[~haythemkh] I wanted to follow up with you. I'd love to see this
contribution, can you tag me if you make some progress on it?
> Solr Example should prompt for ZK port
> --
>
> Key: SOLR-16124
> URL: https://issues.apache.org/jira/browse/SOLR-16124
> Project: Solr
> Issue Type: Improvement
> Components: documentation
>Reporter: Mike Drob
>Priority: Major
> Labels: newdev
>
> Running {{bin/solr start -e cloud}} prompts the user for solr ports, but
> auto-picks the ZK port as first solr port + 1000. We should allow the user to
> customize that in case something else is running on that port already.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Commented] (SOLR-6756) The cloud-dev scripts do not seem to work with the new example layout.
[ https://issues.apache.org/jira/browse/SOLR-6756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17896888#comment-17896888 ] Eric Pugh commented on SOLR-6756: - Mark, can we close this? I think this has been resolved, and if it isn't, I'd love to help and get this sorted! > The cloud-dev scripts do not seem to work with the new example layout. > -- > > Key: SOLR-6756 > URL: https://issues.apache.org/jira/browse/SOLR-6756 > Project: Solr > Issue Type: Bug > Components: SolrCloud >Reporter: Mark Miller >Assignee: Mark Miller >Priority: Major > Fix For: 6.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Resolved] (SOLR-1252) A lighter version of Solr for distribution
[ https://issues.apache.org/jira/browse/SOLR-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Pugh resolved SOLR-1252. - Resolution: Implemented This has been sorted out with our new -slim distributions. If I am not understanding properly, please reopen this ticket! > A lighter version of Solr for distribution > -- > > Key: SOLR-1252 > URL: https://issues.apache.org/jira/browse/SOLR-1252 > Project: Solr > Issue Type: New Feature >Reporter: Noble Paul >Priority: Major > > see the thread > http://markmail.org/thread/z3ukgcowzdsdp3i3 > Let us decide on what all could be included in the lite version. > I guess it should containe > * solr.war > * a single core example > * a multicore example -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Commented] (SOLR-6948) "bin/solr -e cloud" shouldn't bother to ask about collection options if it already exists
[
https://issues.apache.org/jira/browse/SOLR-6948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17896898#comment-17896898
]
Eric Pugh commented on SOLR-6948:
-
[~hossman] do you think this is still a valid issue? SHould we try and get it
to done?
> "bin/solr -e cloud" shouldn't bother to ask about collection options if it
> already exists
> -
>
> Key: SOLR-6948
> URL: https://issues.apache.org/jira/browse/SOLR-6948
> Project: Solr
> Issue Type: Improvement
>Reporter: Chris M. Hostetter
>Assignee: Timothy Potter
>Priority: Minor
>
> if you run "bin/solr -e cloud" and select all defaults, and then later you
> run it again the output looks like this...
> {noformat}
> ...
> Now let's create a new collection for indexing documents in your 2-node
> cluster.
> Please provide a name for your new collection: [gettingstarted]
> gettingstarted
> How many shards would you like to split gettingstarted into? [2]
> 2
> How many replicas per shard would you like to create? [2]
> 2
> Please choose a configuration for the gettingstarted collection, available
> options are:
> basic_configs, data_driven_schema_configs, or sample_techproducts_configs
> [data_driven_schema_configs]
> Connecting to ZooKeeper at localhost:9983
> Collection 'gettingstarted' already exists!
> Checked collection existence using Collections API command:
> http://127.0.1.1:8983/solr/admin/collections?action=list
> SolrCloud example running, please visit http://localhost:8983/solr
> {noformat}
> ...instead of asking about shards, replicas, and config set the cloud example
> should probably check for hte existing of the collection name as soon as the
> user supplies a name, and then exit immediately with just the final part...
> {noformat}
> Now let's create a new collection for indexing documents in your 2-node
> cluster.
> Please provide a name for your new collection: [gettingstarted]
> gettingstarted
> Collection 'gettingstarted' already exists!
> Checked collection existence using Collections API command:
> http://127.0.1.1:8983/solr/admin/collections?action=list
> SolrCloud example running, please visit http://localhost:8983/solr
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
Re: [PR] SOLR-17483: Backport cleanup zk-related logic in bin/solr.cmd [solr]
malliaridis commented on PR #2823: URL: https://github.com/apache/solr/pull/2823#issuecomment-2466203833 It seems to be backwards compatible, so there is probably no issues backport this to branch_9_7 as well. :) -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Commented] (SOLR-17508) Integration tests of bin/solr.cmd on Windows
[ https://issues.apache.org/jira/browse/SOLR-17508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17896925#comment-17896925 ] Christos Malliaridis commented on SOLR-17508: - I'd love to see a more cross-platform implementation for both the CLI and tests and avoid duplicating the logic for each platform. I am experimenting with a Kotlin CLI implementation using Clikt and I was already able to start a Solr instance with a generated script (gradle application) and the entire logic of argument parsing in Kotlin. This means that it is possible to migrate the scripts even further and have more code live inside Java, rather than in the CLI scripts. If we use a script only as an entrypoint to pass the arguments from the CLI to a java application / class, we could write all tests with JUnit. > Integration tests of bin/solr.cmd on Windows > > > Key: SOLR-17508 > URL: https://issues.apache.org/jira/browse/SOLR-17508 > Project: Solr > Issue Type: Task > Components: scripts and tools, test-framework >Reporter: Jan Høydahl >Priority: Major > > For Linux we have BATS that runs integration tests. For Windows we do not > have anything, so it is not uncommon that bin/solr.cmd is buggy after > touching the scripts. > In this issue I propose looking at [https://github.com/pester/Pester] to try > to write some integration tests for bin/solr.cmd. It is a test framework for > Powershell, and is able to execute commands and check their output. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
Re: [PR] chore(deps): update io.netty:* to v4.1.114.final [solr]
malliaridis merged PR #2702: URL: https://github.com/apache/solr/pull/2702 -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Commented] (SOLR-17484) Prometheus Exporter should efficiently work without ZK dependency
[ https://issues.apache.org/jira/browse/SOLR-17484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17896929#comment-17896929 ] David Smiley commented on SOLR-17484: - [~malliaridis] I assume you mis-attributed your commit > Prometheus Exporter should efficiently work without ZK dependency > - > > Key: SOLR-17484 > URL: https://issues.apache.org/jira/browse/SOLR-17484 > Project: Solr > Issue Type: Improvement > Components: contrib - prometheus-exporter >Reporter: David Smiley >Priority: Major > > The Prometheus Exporter, when pointing at SolrCloud, CloudSolrClient with a > ZK connecting backing it. This issue proposes switching it to the Solr/HTTP > based ClusterState provider. > Note there are some performance issues with calls it makes to > CloudSolrClient.getClusterState which shifts from a simple getter to a remote > call that returns the entire cluster state. Perhaps out of scope or a > dependency? -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Updated] (SOLR-4018) Dispatcher to optionally write QTime and Hits HTTP header
[
https://issues.apache.org/jira/browse/SOLR-4018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley updated SOLR-4018:
---
Fix Version/s: (was: 4.9)
(was: 6.0)
> Dispatcher to optionally write QTime and Hits HTTP header
> -
>
> Key: SOLR-4018
> URL: https://issues.apache.org/jira/browse/SOLR-4018
> Project: Solr
> Issue Type: Improvement
>Affects Versions: 4.0
>Reporter: Markus Jelsma
>Priority: Major
> Attachments: SOLR-4018-trunk-1.patch, SOLR-4018-trunk-2.patch,
> SOLR-4018-trunk-3.patch, SOLR-4018-trunk-4.patch, SOLR-4018-trunk-5.patch
>
>
> SolrDispatchFilter should be able to write QTime and Hits HTTP headers via
> configuration.
> {code}
>
> multipartUploadLimitInKB="2048000" />
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Resolved] (SOLR-5091) Clean up Servlets APIs, Kill SolrDispatchFilter, simplify API creation
[ https://issues.apache.org/jira/browse/SOLR-5091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Smiley resolved SOLR-5091. Fix Version/s: (was: 6.0) Resolution: Abandoned Restlet is gone. Container agnostic is decidedly a non-goal. I like some of the ideas in the patch... but I think this issue & code is maybe too old to be useful anyone. I think this issue was maybe doing too much at once. > Clean up Servlets APIs, Kill SolrDispatchFilter, simplify API creation > -- > > Key: SOLR-5091 > URL: https://issues.apache.org/jira/browse/SOLR-5091 > Project: Solr > Issue Type: Improvement >Reporter: Grant Ingersoll >Assignee: Grant Ingersoll >Priority: Major > Attachments: SOLR-5091.patch > > > This is an issue to track a series of sub issues related to deprecated and > crufty Servlet/REST API code. I'll create sub-tasks to manage them. > # Clean up all the old UI stuff (old redirects) > # Kill/Simplify SolrDispatchFilter -- for instance, why not make the user > always have a core name in 5.0? i.e. /collection1 is the default core > ## I'd like to move to just using Guice's servlet extension to do this, > which, I think will also make it easier to run Solr in other containers (i.e. > non-servlet environments) due to the fact that you don't have to tie the > request handling logic specifically to a Servlet. > # Simplify the creation and testing of REST and other APIs via Guice + > Restlet, which I've done on a number of occasions. > ## It might be also possible to move all of the APIs onto Restlet and > maintain back compat through a simple restlet proxy (still exploring this). > This would also have the benefit of abstracting the core request processing > out of the Servlet context and make that an implementation detail. > ## Moving to Guice, IMO, will make it easier to isolate and test individual > components by being able to inject mocks easier. > I am close to a working patch for some of this. I will post incremental > updates/issues as I move forward on this, but I think we should take 5.x as > an opportunity to be more agnostic of container and I believe the approach I > have in mind will do so. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Assigned] (SOLR-17551) zk upconfig command broken on Windows
[
https://issues.apache.org/jira/browse/SOLR-17551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christos Malliaridis reassigned SOLR-17551:
---
Assignee: Christos Malliaridis
> zk upconfig command broken on Windows
> -
>
> Key: SOLR-17551
> URL: https://issues.apache.org/jira/browse/SOLR-17551
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
>Affects Versions: 9.7
> Environment: Windows Server 2022, Windows 10
>Reporter: Mingchun Zhao
>Assignee: Christos Malliaridis
>Priority: Critical
> Attachments: SOLR-17551.patch
>
>
> When running the `solr zk upconfig` command on Windows, the following error
> occurs.
> {code:java}
> C:\Program Files\solr-9.7.0\bin>solr zk upconfig -d sitecore_configs -n
> sitecoreconfigset -z 10.1.0.11:2181,10.1.0.12:2181,10.1.0.13:2181
> 'ELSE' is not recognized as an internal or external command,
> operable program or batch file.
> Failed to parse command-line arguments due to: Unrecognized option: --zk-host
> ZK_HOSTusage: bin/solr upconfig -d -n [-url ] [-z
> ]List of options:
> -d,--conf-dir Local directory with configs.
> -n,--conf-name Configset name in ZooKeeper.
> -url,--solr-url Base Solr URL, which can be used to determine the
> zk-host if that's not known; defaults to:
> http://Solrcloud-test-Solr01:8983.
> -z,--zk-host Zookeeper connection string; unnecessary if ZK_HOST
> is defined in solr.in.sh; otherwise,
> defaults to localhost:9983.Please see the Reference
> Guide for more tools documentation:
> https://solr.apache.org/guide/solr/latest/deployment-guide/solr-control-script-reference.html
> WARN - 2024-11-07 11:29:32.428; org.apache.solr.common.cloud.SolrZkClient;
> Using default ZkCredentialsInjector. ZkCredentialsInjector is not secure, it
> creates an empty list of credentials which leads to 'OPEN_ACL_UNSAFE' ACLs to
> Zookeeper nodes
> WARN - 2024-11-07 11:29:33.666; org.apache.solr.common.cloud.SolrZkClient;
> Using default ZkACLProvider. DefaultZkACLProvider is not secure, it creates
> 'OPEN_ACL_UNSAFE' ACLs to Zookeeper nodes
> Uploading C:\Program
> Files\solr-9.7.0\server\solr\configsets\sitecore_configs\conf for config
> sitecoreconfigset to ZooKeeper at 10.1.0.11:2181 {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Resolved] (SOLR-4018) Dispatcher to optionally write QTime and Hits HTTP header
[
https://issues.apache.org/jira/browse/SOLR-4018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley resolved SOLR-4018.
Resolution: Won't Fix
I completely disagree that SolrDispatchFilter should be doing such things.
SolrDispatchFilter should only to HTTP integration stuff.
> Dispatcher to optionally write QTime and Hits HTTP header
> -
>
> Key: SOLR-4018
> URL: https://issues.apache.org/jira/browse/SOLR-4018
> Project: Solr
> Issue Type: Improvement
>Affects Versions: 4.0
>Reporter: Markus Jelsma
>Priority: Major
> Fix For: 6.0, 4.9
>
> Attachments: SOLR-4018-trunk-1.patch, SOLR-4018-trunk-2.patch,
> SOLR-4018-trunk-3.patch, SOLR-4018-trunk-4.patch, SOLR-4018-trunk-5.patch
>
>
> SolrDispatchFilter should be able to write QTime and Hits HTTP headers via
> configuration.
> {code}
>
> multipartUploadLimitInKB="2048000" />
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
Re: [PR] SOLR-17533: Rearrange and cleanup solr.cmd [solr]
malliaridis merged PR #2822: URL: https://github.com/apache/solr/pull/2822 -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Updated] (SOLR-17551) zk upconfig command broken on Windows
[
https://issues.apache.org/jira/browse/SOLR-17551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christos Malliaridis updated SOLR-17551:
Labels: newdev (was: )
> zk upconfig command broken on Windows
> -
>
> Key: SOLR-17551
> URL: https://issues.apache.org/jira/browse/SOLR-17551
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
>Affects Versions: 9.7
> Environment: Windows Server 2022, Windows 10
>Reporter: Mingchun Zhao
>Assignee: Christos Malliaridis
>Priority: Critical
> Labels: newdev
> Attachments: SOLR-17551.patch
>
>
> When running the `solr zk upconfig` command on Windows, the following error
> occurs.
> {code:java}
> C:\Program Files\solr-9.7.0\bin>solr zk upconfig -d sitecore_configs -n
> sitecoreconfigset -z 10.1.0.11:2181,10.1.0.12:2181,10.1.0.13:2181
> 'ELSE' is not recognized as an internal or external command,
> operable program or batch file.
> Failed to parse command-line arguments due to: Unrecognized option: --zk-host
> ZK_HOSTusage: bin/solr upconfig -d -n [-url ] [-z
> ]List of options:
> -d,--conf-dir Local directory with configs.
> -n,--conf-name Configset name in ZooKeeper.
> -url,--solr-url Base Solr URL, which can be used to determine the
> zk-host if that's not known; defaults to:
> http://Solrcloud-test-Solr01:8983.
> -z,--zk-host Zookeeper connection string; unnecessary if ZK_HOST
> is defined in solr.in.sh; otherwise,
> defaults to localhost:9983.Please see the Reference
> Guide for more tools documentation:
> https://solr.apache.org/guide/solr/latest/deployment-guide/solr-control-script-reference.html
> WARN - 2024-11-07 11:29:32.428; org.apache.solr.common.cloud.SolrZkClient;
> Using default ZkCredentialsInjector. ZkCredentialsInjector is not secure, it
> creates an empty list of credentials which leads to 'OPEN_ACL_UNSAFE' ACLs to
> Zookeeper nodes
> WARN - 2024-11-07 11:29:33.666; org.apache.solr.common.cloud.SolrZkClient;
> Using default ZkACLProvider. DefaultZkACLProvider is not secure, it creates
> 'OPEN_ACL_UNSAFE' ACLs to Zookeeper nodes
> Uploading C:\Program
> Files\solr-9.7.0\server\solr\configsets\sitecore_configs\conf for config
> sitecoreconfigset to ZooKeeper at 10.1.0.11:2181 {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Updated] (SOLR-17551) zk upconfig command broken on Windows
[
https://issues.apache.org/jira/browse/SOLR-17551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christos Malliaridis updated SOLR-17551:
Labels: cli newdev (was: newdev)
> zk upconfig command broken on Windows
> -
>
> Key: SOLR-17551
> URL: https://issues.apache.org/jira/browse/SOLR-17551
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
>Affects Versions: 9.7
> Environment: Windows Server 2022, Windows 10
>Reporter: Mingchun Zhao
>Assignee: Christos Malliaridis
>Priority: Critical
> Labels: cli, newdev
> Attachments: SOLR-17551.patch
>
>
> When running the `solr zk upconfig` command on Windows, the following error
> occurs.
> {code:java}
> C:\Program Files\solr-9.7.0\bin>solr zk upconfig -d sitecore_configs -n
> sitecoreconfigset -z 10.1.0.11:2181,10.1.0.12:2181,10.1.0.13:2181
> 'ELSE' is not recognized as an internal or external command,
> operable program or batch file.
> Failed to parse command-line arguments due to: Unrecognized option: --zk-host
> ZK_HOSTusage: bin/solr upconfig -d -n [-url ] [-z
> ]List of options:
> -d,--conf-dir Local directory with configs.
> -n,--conf-name Configset name in ZooKeeper.
> -url,--solr-url Base Solr URL, which can be used to determine the
> zk-host if that's not known; defaults to:
> http://Solrcloud-test-Solr01:8983.
> -z,--zk-host Zookeeper connection string; unnecessary if ZK_HOST
> is defined in solr.in.sh; otherwise,
> defaults to localhost:9983.Please see the Reference
> Guide for more tools documentation:
> https://solr.apache.org/guide/solr/latest/deployment-guide/solr-control-script-reference.html
> WARN - 2024-11-07 11:29:32.428; org.apache.solr.common.cloud.SolrZkClient;
> Using default ZkCredentialsInjector. ZkCredentialsInjector is not secure, it
> creates an empty list of credentials which leads to 'OPEN_ACL_UNSAFE' ACLs to
> Zookeeper nodes
> WARN - 2024-11-07 11:29:33.666; org.apache.solr.common.cloud.SolrZkClient;
> Using default ZkACLProvider. DefaultZkACLProvider is not secure, it creates
> 'OPEN_ACL_UNSAFE' ACLs to Zookeeper nodes
> Uploading C:\Program
> Files\solr-9.7.0\server\solr\configsets\sitecore_configs\conf for config
> sitecoreconfigset to ZooKeeper at 10.1.0.11:2181 {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
Re: [PR] SOLR-17406: Introduce Version Catalogs [solr]
malliaridis commented on PR #2706: URL: https://github.com/apache/solr/pull/2706#issuecomment-2466308671 The current state should differ now only in hamcrest-core, which is being merged with hamcrest in the `dependencies.gradle`. -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
Re: [PR] CLI: Improve console output of auth command [solr]
malliaridis commented on PR #2857: URL: https://github.com/apache/solr/pull/2857#issuecomment-2466311070 @epugh Is something like this worth a ticket or added in the changes (planning to backport it)? -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Commented] (SOLR-17533) Rearrange and cleanup solr.cmd
[ https://issues.apache.org/jira/browse/SOLR-17533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17896942#comment-17896942 ] ASF subversion and git services commented on SOLR-17533: Commit bc0c226c8fe9c475e5e723355f729fd39ceaf30f in solr's branch refs/heads/main from Christos Malliaridis [ https://gitbox.apache.org/repos/asf?p=solr.git;h=bc0c226c8fe ] SOLR-17533: Rearrange and cleanup solr.cmd (#2822) * Remove ZK logic from solr.cmd This part of the script is not reachable anymore. * Fix unreachable auth tool in solr.cmd * Fix invalid references * Rearrange and cleanup solr.cmd > Rearrange and cleanup solr.cmd > -- > > Key: SOLR-17533 > URL: https://issues.apache.org/jira/browse/SOLR-17533 > Project: Solr > Issue Type: Sub-task > Components: cli >Reporter: Christos Malliaridis >Assignee: Christos Malliaridis >Priority: Minor > Labels: cli, pull-request-available > Time Spent: 1h 10m > Remaining Estimate: 0h > > As mentioned in Solr-17483 the bin/solr.cmd script can be further be improved > and cleaned up by rearranging some of its content and let the java classes > handle more of the argument parsing. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Updated] (SOLR-17483) bin/solr.cmd run_zk method can be drastically simplified
[ https://issues.apache.org/jira/browse/SOLR-17483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christos Malliaridis updated SOLR-17483: Resolution: Fixed Status: Resolved (was: Patch Available) > bin/solr.cmd run_zk method can be drastically simplified > > > Key: SOLR-17483 > URL: https://issues.apache.org/jira/browse/SOLR-17483 > Project: Solr > Issue Type: Sub-task > Components: cli >Affects Versions: 9.8 >Reporter: Eric Pugh >Assignee: Christos Malliaridis >Priority: Minor > Labels: pull-request-available > Fix For: main (10.0), 9.8 > > Time Spent: 2.5h > Remaining Estimate: 0h > > In the bin/solr.cmd windows script, the :run_zk method still has all the > logic for validating arguments. However, we can now rely on the java code > for that. > I suspect there are other opportunities for shrinking bin/solr.cmd as well > now that argument parsing/handling is in Java. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Resolved] (SOLR-17533) Rearrange and cleanup solr.cmd
[ https://issues.apache.org/jira/browse/SOLR-17533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christos Malliaridis resolved SOLR-17533. - Fix Version/s: main (10.0) Resolution: Fixed > Rearrange and cleanup solr.cmd > -- > > Key: SOLR-17533 > URL: https://issues.apache.org/jira/browse/SOLR-17533 > Project: Solr > Issue Type: Sub-task > Components: cli >Reporter: Christos Malliaridis >Assignee: Christos Malliaridis >Priority: Minor > Labels: cli, pull-request-available > Fix For: main (10.0) > > Time Spent: 1h 10m > Remaining Estimate: 0h > > As mentioned in Solr-17483 the bin/solr.cmd script can be further be improved > and cleaned up by rearranging some of its content and let the java classes > handle more of the argument parsing. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Updated] (SOLR-17483) bin/solr.cmd run_zk method can be drastically simplified
[ https://issues.apache.org/jira/browse/SOLR-17483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christos Malliaridis updated SOLR-17483: Fix Version/s: (was: main (10.0)) > bin/solr.cmd run_zk method can be drastically simplified > > > Key: SOLR-17483 > URL: https://issues.apache.org/jira/browse/SOLR-17483 > Project: Solr > Issue Type: Sub-task > Components: cli >Affects Versions: 9.8 >Reporter: Eric Pugh >Assignee: Christos Malliaridis >Priority: Minor > Labels: pull-request-available > Fix For: 9.8 > > Time Spent: 2.5h > Remaining Estimate: 0h > > In the bin/solr.cmd windows script, the :run_zk method still has all the > logic for validating arguments. However, we can now rely on the java code > for that. > I suspect there are other opportunities for shrinking bin/solr.cmd as well > now that argument parsing/handling is in Java. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Updated] (SOLR-17483) bin/solr.cmd run_zk method can be drastically simplified
[ https://issues.apache.org/jira/browse/SOLR-17483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christos Malliaridis updated SOLR-17483: Affects Version/s: (was: 9.8) > bin/solr.cmd run_zk method can be drastically simplified > > > Key: SOLR-17483 > URL: https://issues.apache.org/jira/browse/SOLR-17483 > Project: Solr > Issue Type: Sub-task > Components: cli >Reporter: Eric Pugh >Assignee: Christos Malliaridis >Priority: Minor > Labels: pull-request-available > Fix For: 9.8 > > Time Spent: 2.5h > Remaining Estimate: 0h > > In the bin/solr.cmd windows script, the :run_zk method still has all the > logic for validating arguments. However, we can now rely on the java code > for that. > I suspect there are other opportunities for shrinking bin/solr.cmd as well > now that argument parsing/handling is in Java. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Commented] (SOLR-17484) Prometheus Exporter should efficiently work without ZK dependency
[ https://issues.apache.org/jira/browse/SOLR-17484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17896945#comment-17896945 ] David Smiley commented on SOLR-17484: - FWIW I found that script to be too painful if there's a conflict. I just bail immediately and do the cherrypick manually, which really isn't that hard. > Prometheus Exporter should efficiently work without ZK dependency > - > > Key: SOLR-17484 > URL: https://issues.apache.org/jira/browse/SOLR-17484 > Project: Solr > Issue Type: Improvement > Components: contrib - prometheus-exporter >Reporter: David Smiley >Priority: Major > > The Prometheus Exporter, when pointing at SolrCloud, CloudSolrClient with a > ZK connecting backing it. This issue proposes switching it to the Solr/HTTP > based ClusterState provider. > Note there are some performance issues with calls it makes to > CloudSolrClient.getClusterState which shifts from a simple getter to a remote > call that returns the entire cluster state. Perhaps out of scope or a > dependency? -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Updated] (SOLR-17483) bin/solr.cmd run_zk method can be drastically simplified
[ https://issues.apache.org/jira/browse/SOLR-17483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christos Malliaridis updated SOLR-17483: Fix Version/s: main (10.0) 9.8 > bin/solr.cmd run_zk method can be drastically simplified > > > Key: SOLR-17483 > URL: https://issues.apache.org/jira/browse/SOLR-17483 > Project: Solr > Issue Type: Sub-task > Components: cli >Affects Versions: 9.8 >Reporter: Eric Pugh >Assignee: Christos Malliaridis >Priority: Minor > Labels: pull-request-available > Fix For: main (10.0), 9.8 > > Time Spent: 2.5h > Remaining Estimate: 0h > > In the bin/solr.cmd windows script, the :run_zk method still has all the > logic for validating arguments. However, we can now rely on the java code > for that. > I suspect there are other opportunities for shrinking bin/solr.cmd as well > now that argument parsing/handling is in Java. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Resolved] (SOLR-4818) Refactorings to simplify loading, organization, sharing of cores, etc.
[ https://issues.apache.org/jira/browse/SOLR-4818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Smiley resolved SOLR-4818. Resolution: Abandoned Marking this as abandoned. It's an old umbrella issue. > Refactorings to simplify loading, organization, sharing of cores, etc. > -- > > Key: SOLR-4818 > URL: https://issues.apache.org/jira/browse/SOLR-4818 > Project: Solr > Issue Type: Improvement >Reporter: Mikhail Khludnev >Assignee: Grant Ingersoll >Priority: Major > > Hello, > I want to follow up IRC log from SOLR-1393. > At least, questions are: > - how much guice do you accept: should it load only user's plugin or fully > substitute solrconfig.xml? > - is there any observable stages for this migration? > I'm ccing [~grant_ingers...@yahoo.com] [~rcmuir] as persons who provided an > interest or/and concerns about Guice. > Please vote/ban! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Resolved] (SOLR-4312) SolrCloud upgrade path
[
https://issues.apache.org/jira/browse/SOLR-4312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Pugh resolved SOLR-4312.
-
Resolution: Implemented
I believe that this has been completed via our Ref Guide. If there is
something more specific that is needed, and closing this isn't correct, then
please reopen, and let's figure out what we need! I do see a whole set of
folks currently doing their 8.11 to 9.7 upgrades, so if we are missing content,
we should get it in. And when 10 comes out, that will spark another set of
upgrading ;).
> SolrCloud upgrade path
> --
>
> Key: SOLR-4312
> URL: https://issues.apache.org/jira/browse/SOLR-4312
> Project: Solr
> Issue Type: Task
> Components: SolrCloud
>Affects Versions: 4.0, 4.1
>Reporter: Steven Rowe
>Priority: Major
>
> Upgrading from one SolrCloud version to another needs to be figured out and
> documented.
> Mark Miller wrote on the 4.1 VOTE email on dev@l.a.o:
> {quote}
> One issue that is probably still a problem is that you can't easily upgrade
> form a 4.0 to 4.1 SolrCloud setup in some cases - at least to my knowledge. I
> don't know all the details, but at a minimum, we should probably add an entry
> to changes about what you should do. It may require blowing away your own
> clusterstate.json and re doing your numShards settings, or starting over,
> or…I don't really know. I don't think anyone has tested.
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Commented] (SOLR-17551) zk upconfig command broken on Windows
[
https://issues.apache.org/jira/browse/SOLR-17551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17896904#comment-17896904
]
Christos Malliaridis commented on SOLR-17551:
-
To guarantee backwards compatibility we should go for the patch here. In 9.7 we
still make use of the unused ZK block, and it also covers a few deprecations
that we probably don't support anymore.
> zk upconfig command broken on Windows
> -
>
> Key: SOLR-17551
> URL: https://issues.apache.org/jira/browse/SOLR-17551
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
>Affects Versions: 9.7
> Environment: Windows Server 2022, Windows 10
>Reporter: Mingchun Zhao
>Priority: Critical
> Attachments: SOLR-17551.patch
>
>
> When running the `solr zk upconfig` command on Windows, the following error
> occurs.
> {code:java}
> C:\Program Files\solr-9.7.0\bin>solr zk upconfig -d sitecore_configs -n
> sitecoreconfigset -z 10.1.0.11:2181,10.1.0.12:2181,10.1.0.13:2181
> 'ELSE' is not recognized as an internal or external command,
> operable program or batch file.
> Failed to parse command-line arguments due to: Unrecognized option: --zk-host
> ZK_HOSTusage: bin/solr upconfig -d -n [-url ] [-z
> ]List of options:
> -d,--conf-dir Local directory with configs.
> -n,--conf-name Configset name in ZooKeeper.
> -url,--solr-url Base Solr URL, which can be used to determine the
> zk-host if that's not known; defaults to:
> http://Solrcloud-test-Solr01:8983.
> -z,--zk-host Zookeeper connection string; unnecessary if ZK_HOST
> is defined in solr.in.sh; otherwise,
> defaults to localhost:9983.Please see the Reference
> Guide for more tools documentation:
> https://solr.apache.org/guide/solr/latest/deployment-guide/solr-control-script-reference.html
> WARN - 2024-11-07 11:29:32.428; org.apache.solr.common.cloud.SolrZkClient;
> Using default ZkCredentialsInjector. ZkCredentialsInjector is not secure, it
> creates an empty list of credentials which leads to 'OPEN_ACL_UNSAFE' ACLs to
> Zookeeper nodes
> WARN - 2024-11-07 11:29:33.666; org.apache.solr.common.cloud.SolrZkClient;
> Using default ZkACLProvider. DefaultZkACLProvider is not secure, it creates
> 'OPEN_ACL_UNSAFE' ACLs to Zookeeper nodes
> Uploading C:\Program
> Files\solr-9.7.0\server\solr\configsets\sitecore_configs\conf for config
> sitecoreconfigset to ZooKeeper at 10.1.0.11:2181 {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
Re: [PR] SOLR-17533: Rearrange and cleanup solr.cmd [solr]
malliaridis commented on code in PR #2822: URL: https://github.com/apache/solr/pull/2822#discussion_r1835368230 ## solr/bin/solr.cmd: ## @@ -383,18 +355,19 @@ goto done @echo. goto done - -REM Really basic command-line arg parsing +REM Parse arguments for special commands (start, stop, restart) Review Comment: This part is skipped in case of the auth command. The auth command has its own parsing plus the java class parsing. If I am not mistaken, this was the same behavior before and if I am not mistaken `bin/solr` does the same. Correct me if I am wrong though. -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
[PR] Improve console output of auth command [solr]
malliaridis opened a new pull request, #2857: URL: https://github.com/apache/solr/pull/2857 # Description The console is currently printing the username and password when the user enables authentication via ```bash bin/solr auth enable --prompt true ``` This defeats the purpose of a hidden password prompt. # Solution Do not print the password when basic authentication is enabled. -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
[PR] Opinion piece on Scaling Solr [solr-site]
epugh opened a new pull request, #132: URL: https://github.com/apache/solr-site/pull/132 (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-mail: issues-unsubscr...@solr.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
