[jira] [Commented] (SOLR-17068) Migrate Ref Guide content to using bin/solr post command
[ https://issues.apache.org/jira/browse/SOLR-17068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17811668#comment-17811668 ] Eric Pugh commented on SOLR-17068: -- I am looking at this again. What do folks think about just removing bin/post from the 9X line in favour of bin/solr post? That would make life easier then trying to have bin/post and bin/solr post work in 9x, and then only having bin/solr post in 10x > Migrate Ref Guide content to using bin/solr post command > > > Key: SOLR-17068 > URL: https://issues.apache.org/jira/browse/SOLR-17068 > Project: Solr > Issue Type: Sub-task > Components: documentation >Affects Versions: 9.4 >Reporter: Eric Pugh >Priority: Minor > > The Ref Guide has many references to the old bin/post command (and it's > sibling awkward windows version) while ALSO having bin/solr post commands. > We need to finish the migration to bin/solr post so we don't have a awkward > split of both approaches. -- 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
[PR] SOLR-17068: Resolve mish mash of bin/post and bin/solr post references in favour of bin/solr post. [solr]
epugh opened a new pull request, #2227: URL: https://github.com/apache/solr/pull/2227 https://issues.apache.org/jira/browse/SOLR-17068 # Description Removing old bin/post references. # Solution Clean ups through out docs and code base. # Tests Bats and unit tests. # 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. - [X ] 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) - [ X] I have developed this patch against the `main` branch. - [ X] I have run `./gradlew check`. - [ X] I have added tests for my changes. - [ X] 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
Re: [PR] SOLR-17131: Optimize rows=0 since score/sort isn't necessary [solr]
dsmiley commented on PR #2221: URL: https://github.com/apache/solr/pull/2221#issuecomment-1913695210 I also think a `queryResultWindowSize` of 1 (which is the default if it isn't specified in solrconfig and isn't documented AFAICT) should not bump up a request for no rows to a window of a paltry 1 doc. I don't think that was intended; I think what was intended was to effectively have no window if it isn't specified. I can see using a default of 1 _seems_ to convey that (for typical queries that have results) but not for rows=0 case. Likely an oversight long ago. -- 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-17126) Cut over System.getProperty to EnvUtils.getProperty
[ https://issues.apache.org/jira/browse/SOLR-17126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl updated SOLR-17126: --- Fix Version/s: 9.6.0 > Cut over System.getProperty to EnvUtils.getProperty > --- > > Key: SOLR-17126 > URL: https://issues.apache.org/jira/browse/SOLR-17126 > Project: Solr > Issue Type: Task > Security Level: Public(Default Security Level. Issues are Public) >Reporter: Jan Høydahl >Assignee: Jan Høydahl >Priority: Major > Fix For: 9.6.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Followup from SOLR-15960. This will handle all modules. > Let's create several PRs on the same CHANGES entry for migrations happening > in the 9.6 release. -- 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] GH Labeler action: Category labels [solr]
janhoy commented on PR #2190: URL: https://github.com/apache/solr/pull/2190#issuecomment-1913734064 Did some consolidation, now down to 9 new category labels: > api, cli, cloud, index, metrics, packagemanager, schema, search, security -- 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-16935 Add spans to cover gaps in query processing [solr]
github-actions[bot] commented on PR #1853: URL: https://github.com/apache/solr/pull/1853#issuecomment-1913767966 This PR had no visible activity in the past 60 days, labeling it as stale. Any new activity will remove the stale label. To attract more reviewers, please tag someone or notify the d...@solr.apache.org mailing list. 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
[jira] [Created] (SOLR-17132) LTR model upload API issue
rajanimaski created SOLR-17132: -- Summary: LTR model upload API issue Key: SOLR-17132 URL: https://issues.apache.org/jira/browse/SOLR-17132 Project: Solr Issue Type: Improvement Security Level: Public (Default Security Level. Issues are Public) Components: contrib - LTR Affects Versions: 9.4.1 Reporter: rajanimaski The LTR model upload API does not make the model available across all the nodes. After upload, "model not found exception" is reported by certain nodes. The model becomes available only after a collection "reload" api is requested. -- 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-17132) LTR model upload API issue
[ https://issues.apache.org/jira/browse/SOLR-17132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17811721#comment-17811721 ] rajanimaski commented on SOLR-17132: Suggestion from [~ishan] - LTR models could take advantage of the File store APIs that was built for distributed management of package files. > LTR model upload API issue > -- > > Key: SOLR-17132 > URL: https://issues.apache.org/jira/browse/SOLR-17132 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) > Components: contrib - LTR >Affects Versions: 9.4.1 >Reporter: rajanimaski >Priority: Major > > The LTR model upload API does not make the model available across all the > nodes. After upload, "model not found exception" is reported by certain > nodes. The model becomes available only after a collection "reload" api is > requested. -- 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
