[jira] [Updated] (SOLR-8409) Complex q param in Streaming Expression results in a bad query
[
https://issues.apache.org/jira/browse/SOLR-8409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Gove updated SOLR-8409:
--
Attachment: SOLR-8409.patch
This new patch ensures that escaped quotes in the parameters of a
CloudSolrStream stream are properly re-escaped when converting back to a string
expression. This is necessary for situations where the expression is passed off
to workers.
Note the comment in CloudSolrStream
{code}
// SOLR-8409: This is a special case where the params contain a "
character
// Do note that in any other BASE streams with parameters where a " might
come into play
// that this same replacement needs to take place.
value = value.replace("\"", "\\\"");
{code}
I hope that this comment is heeded if additional base streams dealing with solr
params are ever added.
> Complex q param in Streaming Expression results in a bad query
> --
>
> Key: SOLR-8409
> URL: https://issues.apache.org/jira/browse/SOLR-8409
> Project: Solr
> Issue Type: Bug
> Components: SolrJ
>Affects Versions: Trunk
>Reporter: Dennis Gove
>Priority: Minor
> Labels: streaming, streaming_api
> Attachments: SOLR-8409.patch, SOLR-8409.patch
>
>
> When providing an expression like
> {code}
> stream=search(people, fl="id,first", sort="first asc",
> q="presentTitles:\"chief executive officer\" AND age:[36 TO *]")
> {code}
> the following error is seen.
> {code}
> no field name specified in query and no default specified via 'df' param
> {code}
> I believe the issue is related to the \" (escaped quotes) and the spaces in
> the q field. If I remove the spaces then the query returns results as
> expected (though I've yet to validate if those results are accurate).
> This requires some investigation to get down to the root cause. I would like
> to fix it before Solr 6 is cut.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-8409) Complex q param in Streaming Expression results in a bad query
[
https://issues.apache.org/jira/browse/SOLR-8409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Gove updated SOLR-8409:
--
Attachment: SOLR-8409.patch
This patch **appears** to fix the issues. Still am unable to replicate in a
unit test but I have confirmed that the issue I was seeing in a packaged setup
is fixed with this patch.
I'll want to wait until I can get a replicated test before I commit this.
> Complex q param in Streaming Expression results in a bad query
> --
>
> Key: SOLR-8409
> URL: https://issues.apache.org/jira/browse/SOLR-8409
> Project: Solr
> Issue Type: Bug
> Components: SolrJ
>Affects Versions: Trunk, 6.0
>Reporter: Dennis Gove
>Priority: Minor
> Labels: streaming, streaming_api
> Attachments: SOLR-8409.patch
>
>
> When providing an expression like
> {code}
> stream=search(people, fl="id,first", sort="first asc",
> q="presentTitles:\"chief executive officer\" AND age:[36 TO *]")
> {code}
> the following error is seen.
> {code}
> no field name specified in query and no default specified via 'df' param
> {code}
> I believe the issue is related to the \" (escaped quotes) and the spaces in
> the q field. If I remove the spaces then the query returns results as
> expected (though I've yet to validate if those results are accurate).
> This requires some investigation to get down to the root cause. I would like
> to fix it before Solr 6 is cut.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-8409) Complex q param in Streaming Expression results in a bad query
[
https://issues.apache.org/jira/browse/SOLR-8409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Gove updated SOLR-8409:
--
Description:
When providing an expression like
{code}
stream=search(people, fl="id,first", sort="first asc", q="presentTitles:\"chief
executive officer\" AND age:[36 TO *]")
{code}
the following error is seen.
{code}
no field name specified in query and no default specified via 'df' param
{code}
I believe the issue is related to the \" (escaped quotes) and the spaces in the
q field. If I remove the spaces then the query returns results as expected
(though I've yet to validate if those results are accurate).
This requires some investigation to get down to the root cause. I would like to
fix it before Solr 6 is cut.
was:
When providing an expression like
{code}
expression=search(people, fl="id,first", sort="first asc",
q="presentTitles:\"chief executive officer\" AND age:[36 TO *]")
{code}
the following error is seen.
{code}
no field name specified in query and no default specified via 'df' param
{code}
I believe the issue is related to the \" (escaped quotes) and the spaces in the
q field. If I remove the spaces then the query returns results as expected
(though I've yet to validate if those results are accurate).
This requires some investigation to get down to the root cause. I would like to
fix it before Solr 6 is cut.
> Complex q param in Streaming Expression results in a bad query
> --
>
> Key: SOLR-8409
> URL: https://issues.apache.org/jira/browse/SOLR-8409
> Project: Solr
> Issue Type: Bug
> Components: SolrJ
>Affects Versions: Trunk, 6.0
>Reporter: Dennis Gove
>Priority: Minor
> Labels: streaming, streaming_api
>
> When providing an expression like
> {code}
> stream=search(people, fl="id,first", sort="first asc",
> q="presentTitles:\"chief executive officer\" AND age:[36 TO *]")
> {code}
> the following error is seen.
> {code}
> no field name specified in query and no default specified via 'df' param
> {code}
> I believe the issue is related to the \" (escaped quotes) and the spaces in
> the q field. If I remove the spaces then the query returns results as
> expected (though I've yet to validate if those results are accurate).
> This requires some investigation to get down to the root cause. I would like
> to fix it before Solr 6 is cut.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-8409) Complex q param in Streaming Expression results in a bad query
[
https://issues.apache.org/jira/browse/SOLR-8409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Gove updated SOLR-8409:
--
Affects Version/s: 6.0
Trunk
Labels: streaming streaming_api (was: )
Description:
When providing an expression like
{code}
expression=search(people, fl="id,first", sort="first asc",
q="presentTitles:\"chief executive officer\" AND age:[36 TO *]")
{code}
the following error is seen.
{code}
no field name specified in query and no default specified via 'df' param
{code}
I believe the issue is related to the \" (escaped quotes) and the spaces in the
q field. If I remove the spaces then the query returns results as expected
(though I've yet to validate if those results are accurate).
This requires some investigation to get down to the root cause. I would like to
fix it before Solr 6 is cut.
> Complex q param in Streaming Expression results in a bad query
> --
>
> Key: SOLR-8409
> URL: https://issues.apache.org/jira/browse/SOLR-8409
> Project: Solr
> Issue Type: Bug
> Components: SolrJ
>Affects Versions: Trunk, 6.0
>Reporter: Dennis Gove
>Priority: Minor
> Labels: streaming, streaming_api
>
> When providing an expression like
> {code}
> expression=search(people, fl="id,first", sort="first asc",
> q="presentTitles:\"chief executive officer\" AND age:[36 TO *]")
> {code}
> the following error is seen.
> {code}
> no field name specified in query and no default specified via 'df' param
> {code}
> I believe the issue is related to the \" (escaped quotes) and the spaces in
> the q field. If I remove the spaces then the query returns results as
> expected (though I've yet to validate if those results are accurate).
> This requires some investigation to get down to the root cause. I would like
> to fix it before Solr 6 is cut.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
