[jira] [Commented] (SOLR-7621) Frequent 500 error IOExceptions from StreamingExpressions

2015-06-01 Thread Hoss Man (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-7621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14568250#comment-14568250
 ] 

Hoss Man commented on SOLR-7621:


my first steps were to startup the cloud example and seed it with some data to 
try and query...

{noformat}
bin/solr -e cloud -noprompt
bin/post -c gettingstarted example/exampledocs/*.xml
{noformat}

(NOTE: because this uses the data driven configs by default, many fields here 
are actually multivalued as a result)

Here's a quick snapshot of one doc in the index using regular search...

{noformat}
curl 'http://localhost:8983/solr/gettingstarted/query?q=id:SOLR1000'
{
  responseHeader:{
status:0,
QTime:15,
params:{
  q:id:SOLR1000}},
  response:{numFound:1,start:0,maxScore:3.1972246,docs:[
  {
id:SOLR1000,
name:[Solr, the Enterprise Search Server],
manu:[Apache Software Foundation],
cat:[software,
  search],
features:[Advanced Full-Text Search Capabilities using Lucene,
  Optimized for High Volume Web Traffic,
  Standards Based Open Interfaces - XML and HTTP,
  Comprehensive HTML Administration Interfaces,
  Scalability - Efficient Replication to other Solr Search Servers,
  Flexible and Adaptable with XML configuration and Schema,
  Good unicode support: héllo (hello with an accent over the e)],
price:[0.0],
popularity:[10],
inStock:[true],
incubationdate_dt:2006-01-17T00:00:00Z,
_version_:1502820680744304640}]
  }}
{noformat}

And here's some results modifying the example from the Streaming Expressions 
documentation against this data.

ask for a sort on the multivalued price field...

{noformat}
curl --data-urlencode 'stream=search(gettingstarted, q=id:SOLR1000, 
fl=id,price, sort=price asc)' 
'http://localhost:8983/solr/gettingstarted/stream?indent=true'
{
  error:{
msg:java.util.concurrent.ExecutionException: java.io.IOException: 
JSONTupleStream: expected ARRAY_START but got EOF,
trace:java.io.IOException: java.util.concurrent.ExecutionException: 
java.io.IOException: JSONTupleStream: expected ARRAY_START but got EOF\n\tat 
org.apache.solr.client.solrj.io.stream.CloudSolrStream.openStreams(CloudSolrStream.java:334)\n\tat
 
org.apache.solr.client.solrj.io.stream.CloudSolrStream.open(CloudSolrStream.java:232)\n\tat
 
org.apache.solr.response.TextResponseWriter.writeTupleStream(TextResponseWriter.java:320)\n\tat
 
org.apache.solr.response.TextResponseWriter.writeVal(TextResponseWriter.java:191)\n\tat
 
org.apache.solr.response.JSONWriter.writeNamedListAsMapWithDups(JSONResponseWriter.java:184)\n\tat
 
org.apache.solr.response.JSONWriter.writeNamedList(JSONResponseWriter.java:300)\n\tat
 
org.apache.solr.response.JSONWriter.writeResponse(JSONResponseWriter.java:96)\n\tat
 
org.apache.solr.response.JSONResponseWriter.write(JSONResponseWriter.java:61)\n\tat
 
org.apache.solr.response.QueryResponseWriterUtil.writeQueryResponse(QueryResponseWriterUtil.java:53)\n\tat
 
org.apache.solr.servlet.HttpSolrCall.writeResponse(HttpSolrCall.java:707)\n\tat 
org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:447)\n\tat 
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:227)\n\tat
 
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:196)\n\tat
 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)\n\tat
 
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)\n\tat
 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)\n\tat
 
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)\n\tat
 
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)\n\tat
 
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)\n\tat
 
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)\n\tat 
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)\n\tat
 
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)\n\tat
 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)\n\tat
 
org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215)\n\tat
 
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:110)\n\tat
 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)\n\tat
 org.eclipse.jetty.server.Server.handle(Server.java:497)\n\tat 
org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:310)\n\tat 
org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257)\n\tat
 
org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540)\n\tat
 

[jira] [Commented] (SOLR-7621) Frequent 500 error IOExceptions from StreamingExpressions

2015-06-01 Thread Joel Bernstein (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-7621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14568356#comment-14568356
 ] 

Joel Bernstein commented on SOLR-7621:
--

Also [~gus_heck] has some error handling improvements in SOLR-7441.

 Frequent 500 error IOExceptions from StreamingExpressions
 -

 Key: SOLR-7621
 URL: https://issues.apache.org/jira/browse/SOLR-7621
 Project: Solr
  Issue Type: Bug
Affects Versions: 5.2
Reporter: Hoss Man
Assignee: Joel Bernstein

 While trying to test out the new Streaming Expressions functionality, I 
 encountered lots of 500 error / IOException with various root causes  (i'll 
 post details in the comments)
 It looks like the API needs to be better hardend to give the user useful 
 feedback and return 4xx errors when used in an incorrect manner



--
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] [Commented] (SOLR-7621) Frequent 500 error IOExceptions from StreamingExpressions

2015-06-01 Thread Dennis Gove (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-7621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14568340#comment-14568340
 ] 

Dennis Gove commented on SOLR-7621:
---

Note that SOLR-7528 adds null checks in the Comparators to allow for null 
values in the sort fields. It considers two null values to be equal. The 
intention is that in a future enhancement we can support a configurable 
approach to how we treat nulls.

 Frequent 500 error IOExceptions from StreamingExpressions
 -

 Key: SOLR-7621
 URL: https://issues.apache.org/jira/browse/SOLR-7621
 Project: Solr
  Issue Type: Bug
Affects Versions: 5.2
Reporter: Hoss Man
Assignee: Joel Bernstein

 While trying to test out the new Streaming Expressions functionality, I 
 encountered lots of 500 error / IOException with various root causes  (i'll 
 post details in the comments)
 It looks like the API needs to be better hardend to give the user useful 
 feedback and return 4xx errors when used in an incorrect manner



--
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] [Commented] (SOLR-7621) Frequent 500 error IOExceptions from StreamingExpressions

2015-06-01 Thread Joel Bernstein (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-7621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14568323#comment-14568323
 ] 

Joel Bernstein commented on SOLR-7621:
--

Initial release requires default values in the sort fields. I can update the 
documentation to reflect this.

Hardening and error handling is a very high priority up and down the Streaming 
stack.

 Frequent 500 error IOExceptions from StreamingExpressions
 -

 Key: SOLR-7621
 URL: https://issues.apache.org/jira/browse/SOLR-7621
 Project: Solr
  Issue Type: Bug
Affects Versions: 5.2
Reporter: Hoss Man
Assignee: Joel Bernstein

 While trying to test out the new Streaming Expressions functionality, I 
 encountered lots of 500 error / IOException with various root causes  (i'll 
 post details in the comments)
 It looks like the API needs to be better hardend to give the user useful 
 feedback and return 4xx errors when used in an incorrect manner



--
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