[jira] [Commented] (SOLR-14384) Stack SolrRequestInfo
[ https://issues.apache.org/jira/browse/SOLR-14384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17136333#comment-17136333 ] ASF subversion and git services commented on SOLR-14384: Commit 35bdf9b413512fa4b2e360df14991f27462ecb6f in lucene-solr's branch refs/heads/branch_8x from Nazerke Seidan [ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=35bdf9b ] SOLR-14384: SolrRequestInfo now stacks internally. * "set" now MUST pair with a "clear" * fixes SolrIndexSearcher.warm which should have re-instated previous SRI * cleans up some SRI set/clear users Closes #1527 (cherry picked from commit 2da71c2a405483e2cf5270dfc20cbd760cd66486) > Stack SolrRequestInfo > - > > Key: SOLR-14384 > URL: https://issues.apache.org/jira/browse/SOLR-14384 > Project: Solr > Issue Type: Improvement >Reporter: David Smiley >Assignee: David Smiley >Priority: Minor > Time Spent: 3h 10m > Remaining Estimate: 0h > > Sometimes SolrRequestInfo need to be suspended/overridden with a new one that > is used temporarily. Examples are in the {{[subquery]}} transformer, and in > warm of caches, and in QuerySenderListener (another type of warming), maybe > others. This can be annoying to do correctly, and in at least one place it > isn't done correctly. SolrRequestInfoSuspender shows some complexity. In > this issue, [~dsmiley] proposes using a stack internally to SolrRequestInfo > that is push'ed and pop'ed. It's not the only way to solve this but it's one > way. > See linked issues for the context and discussion. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Commented] (SOLR-14384) Stack SolrRequestInfo
[ https://issues.apache.org/jira/browse/SOLR-14384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17136323#comment-17136323 ] ASF subversion and git services commented on SOLR-14384: Commit 2da71c2a405483e2cf5270dfc20cbd760cd66486 in lucene-solr's branch refs/heads/master from Nazerke Seidan [ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=2da71c2 ] SOLR-14384: SolrRequestInfo now stacks internally. * "set" now MUST pair with a "clear" * fixes SolrIndexSearcher.warm which should have re-instated previous SRI * cleans up some SRI set/clear users Closes #1527 > Stack SolrRequestInfo > - > > Key: SOLR-14384 > URL: https://issues.apache.org/jira/browse/SOLR-14384 > Project: Solr > Issue Type: Improvement >Reporter: David Smiley >Assignee: David Smiley >Priority: Minor > Time Spent: 3h 10m > Remaining Estimate: 0h > > Sometimes SolrRequestInfo need to be suspended/overridden with a new one that > is used temporarily. Examples are in the {{[subquery]}} transformer, and in > warm of caches, and in QuerySenderListener (another type of warming), maybe > others. This can be annoying to do correctly, and in at least one place it > isn't done correctly. SolrRequestInfoSuspender shows some complexity. In > this issue, [~dsmiley] proposes using a stack internally to SolrRequestInfo > that is push'ed and pop'ed. It's not the only way to solve this but it's one > way. > See linked issues for the context and discussion. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Commented] (SOLR-14384) Stack SolrRequestInfo
[ https://issues.apache.org/jira/browse/SOLR-14384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17134281#comment-17134281 ] David Smiley commented on SOLR-14384: - I'm inclined to merge the PR as-is for master & 8x Monday. > Stack SolrRequestInfo > - > > Key: SOLR-14384 > URL: https://issues.apache.org/jira/browse/SOLR-14384 > Project: Solr > Issue Type: Improvement >Reporter: David Smiley >Assignee: David Smiley >Priority: Minor > Time Spent: 3h > Remaining Estimate: 0h > > Sometimes SolrRequestInfo need to be suspended/overridden with a new one that > is used temporarily. Examples are in the {{[subquery]}} transformer, and in > warm of caches, and in QuerySenderListener (another type of warming), maybe > others. This can be annoying to do correctly, and in at least one place it > isn't done correctly. SolrRequestInfoSuspender shows some complexity. In > this issue, [~dsmiley] proposes using a stack internally to SolrRequestInfo > that is push'ed and pop'ed. It's not the only way to solve this but it's one > way. > See linked issues for the context and discussion. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Commented] (SOLR-14384) Stack SolrRequestInfo
[ https://issues.apache.org/jira/browse/SOLR-14384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127098#comment-17127098 ] David Smiley commented on SOLR-14384: - They could be made to be homogeneous, though I think the likelihood of the two are different. Nesting QParser is very easy, but its not easy to trigger a nested Solr request. It happens in a very limited set of cases that, AFAIK, do not involve user-input. I suppose if you let your users hand-edit join queries then maybe ;-) > Stack SolrRequestInfo > - > > Key: SOLR-14384 > URL: https://issues.apache.org/jira/browse/SOLR-14384 > Project: Solr > Issue Type: Improvement >Reporter: David Smiley >Assignee: David Smiley >Priority: Minor > Time Spent: 3h > Remaining Estimate: 0h > > Sometimes SolrRequestInfo need to be suspended/overridden with a new one that > is used temporarily. Examples are in the {{[subquery]}} transformer, and in > warm of caches, and in QuerySenderListener (another type of warming), maybe > others. This can be annoying to do correctly, and in at least one place it > isn't done correctly. SolrRequestInfoSuspender shows some complexity. In > this issue, [~dsmiley] proposes using a stack internally to SolrRequestInfo > that is push'ed and pop'ed. It's not the only way to solve this but it's one > way. > See linked issues for the context and discussion. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Commented] (SOLR-14384) Stack SolrRequestInfo
[ https://issues.apache.org/jira/browse/SOLR-14384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127093#comment-17127093 ] Mikhail Khludnev commented on SOLR-14384: - [~dsmiley], one question. Why leaking SRI just notifies in logs, but recursion in QParser is guarded with exception? > Stack SolrRequestInfo > - > > Key: SOLR-14384 > URL: https://issues.apache.org/jira/browse/SOLR-14384 > Project: Solr > Issue Type: Improvement >Reporter: David Smiley >Assignee: David Smiley >Priority: Minor > Time Spent: 3h > Remaining Estimate: 0h > > Sometimes SolrRequestInfo need to be suspended/overridden with a new one that > is used temporarily. Examples are in the {{[subquery]}} transformer, and in > warm of caches, and in QuerySenderListener (another type of warming), maybe > others. This can be annoying to do correctly, and in at least one place it > isn't done correctly. SolrRequestInfoSuspender shows some complexity. In > this issue, [~dsmiley] proposes using a stack internally to SolrRequestInfo > that is push'ed and pop'ed. It's not the only way to solve this but it's one > way. > See linked issues for the context and discussion. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Commented] (SOLR-14384) Stack SolrRequestInfo
[ https://issues.apache.org/jira/browse/SOLR-14384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17126935#comment-17126935 ] David Smiley commented on SOLR-14384: - Finally I think the PR is ready. There is a slight doubt in my mind as to wether to tweak anything for the 8x backport. The PR makes SolrRequestInfo rather strict in needing to always clear after a set, and never set too many times or set too little, and can't set null. If you violate these rules, then a ERROR is logged. If assertions are enabled, it'll trip. Maybe just an upgrade note in the ref guide pointing out the strict-ness? Or maybe ERROR is too harsh (do WARN instead)? Or it's all totally fine as-is. > Stack SolrRequestInfo > - > > Key: SOLR-14384 > URL: https://issues.apache.org/jira/browse/SOLR-14384 > Project: Solr > Issue Type: Improvement >Reporter: David Smiley >Assignee: David Smiley >Priority: Minor > Time Spent: 3h > Remaining Estimate: 0h > > Sometimes SolrRequestInfo need to be suspended/overridden with a new one that > is used temporarily. Examples are in the {{[subquery]}} transformer, and in > warm of caches, and in QuerySenderListener (another type of warming), maybe > others. This can be annoying to do correctly, and in at least one place it > isn't done correctly. SolrRequestInfoSuspender shows some complexity. In > this issue, [~dsmiley] proposes using a stack internally to SolrRequestInfo > that is push'ed and pop'ed. It's not the only way to solve this but it's one > way. > See linked issues for the context and discussion. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Commented] (SOLR-14384) Stack SolrRequestInfo
[ https://issues.apache.org/jira/browse/SOLR-14384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17113070#comment-17113070 ] Nazerke Seidan commented on SOLR-14384: --- [~mkhl] I think it is a good idea to add some more information to the description for the clarification purpose. I couldn't edit the description. > Stack SolrRequestInfo > - > > Key: SOLR-14384 > URL: https://issues.apache.org/jira/browse/SOLR-14384 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) >Reporter: Mikhail Khludnev >Priority: Minor > Time Spent: 1h 10m > Remaining Estimate: 0h > > Sometimes SolrRequestInfo need to be suspended or overridden. [~dsmiley] > suggests to introduce stacking for it. See linked issues for the context and > discussion. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Commented] (SOLR-14384) Stack SolrRequestInfo
[ https://issues.apache.org/jira/browse/SOLR-14384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17111627#comment-17111627 ] Noble Paul commented on SOLR-14384: --- Can we have a better description? I'm sure this may be required, but it's not clear why > Stack SolrRequestInfo > - > > Key: SOLR-14384 > URL: https://issues.apache.org/jira/browse/SOLR-14384 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) >Reporter: Mikhail Khludnev >Priority: Minor > Time Spent: 1h 10m > Remaining Estimate: 0h > > Sometimes SolrRequestInfo need to be suspended or overridden. [~dsmiley] > suggests to introduce stacking for it. See linked issues for the context and > discussion. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Commented] (SOLR-14384) Stack SolrRequestInfo
[ https://issues.apache.org/jira/browse/SOLR-14384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17110598#comment-17110598 ] Nazerke Seidan commented on SOLR-14384: --- Hello [~mkhl], I have made a PR to this issue, could you have a look? With [~dsmiley]'s help I refactored the code. > Stack SolrRequestInfo > - > > Key: SOLR-14384 > URL: https://issues.apache.org/jira/browse/SOLR-14384 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) >Reporter: Mikhail Khludnev >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > Sometimes SolrRequestInfo need to be suspended or overridden. [~dsmiley] > suggests to introduce stacking for it. See linked issues for the context and > discussion. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Commented] (SOLR-14384) Stack SolrRequestInfo
[ https://issues.apache.org/jira/browse/SOLR-14384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17106067#comment-17106067 ] Mikhail Khludnev commented on SOLR-14384: - Hi, [~Seidan]. It make sense, if {{TestSubQueryTransformer*}} don't mind. > Stack SolrRequestInfo > - > > Key: SOLR-14384 > URL: https://issues.apache.org/jira/browse/SOLR-14384 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) >Reporter: Mikhail Khludnev >Priority: Minor > > Sometimes SolrRequestInfo need to be suspended or overridden. [~dsmiley] > suggests to introduce stacking for it. See linked issues for the context and > discussion. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Commented] (SOLR-14384) Stack SolrRequestInfo
[ https://issues.apache.org/jira/browse/SOLR-14384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105501#comment-17105501 ] Nazerke Seidan commented on SOLR-14384: --- [~mkhl] , I am working on this issue by introducing suggested stack idea ([~dsmiley] ). I noticed SolrRequestInfoSuspender extends SolrRequestInfo and removes the threadlocal later on. But SolrRequestInfoSuspender is no longer needed now as all SolrRequestInfos are stacked. What do you think if we remove SolrRequestInfoSuspender? > Stack SolrRequestInfo > - > > Key: SOLR-14384 > URL: https://issues.apache.org/jira/browse/SOLR-14384 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) >Reporter: Mikhail Khludnev >Priority: Minor > > Sometimes SolrRequestInfo need to be suspended or overridden. [~dsmiley] > suggests to introduce stacking for it. See linked issues for the context and > discussion. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org