Error for Graph Traversal using Streaming Expressions

2017-03-12 Thread Zheng Lin Edwin Yeo
Hi, I am getting this error when I tried to run a query for Graph Traversal using Streaming Expressions: { "result-set":{ "docs":[{ "EXCEPTION":"java.util.concurrent.ExecutionException: java.lang.RuntimeException: java.io.IOException: java.util.concurrent.ExecutionException: java.io

Re: q=-id:xxxx in export handler does not work but works ok in select.

2017-03-12 Thread Sundeep T
Hi Erick, It looks like solr by default takes care of adding the *:* for /select API for NOT queries like this. In the newer /export API, it is not doing that by default. So, it is kind of inconsistent, and a lot of users will run into this if they try to use the /export api for streaming results

Re: Iterating sorted result docs in a custom search component

2017-03-12 Thread Erick Erickson
This really looks like re-inventing Streaming Aggregation/Streaming Expressions. Admittedly, the processing will probably be faster if done internally, but if response time isn't super-critical you might want consider. If the Streaming stuff (including ParallelSQL) works you will need to upgrade, 6

Re: Iterating sorted result docs in a custom search component

2017-03-12 Thread Joel Bernstein
The /export handler does exactly what you described, but it stream documents rather trying to sort everything in memory at once. In Solr 4.11 the class is called SortingResponseWriter. You can take a look at the approach used. Joel Bernstein http://joelsolr.blogspot.com/ On Sun, Mar 12, 2017 at 8

Re: q=-id:xxxx in export handler does not work but works ok in select.

2017-03-12 Thread Erick Erickson
Oh, you're running into a "quirk" of Solr. Pure negative queries in main clauses require a *:* in front unless there's some special handling. So try: q=*:* -id:8733 instead in both cases. Best, Erick On Sun, Mar 12, 2017 at 7:57 AM, radha krishnan wrote: > q=-id: in export handler does not w

Re: Simple sql query with where clause doesn't work

2017-03-12 Thread Erick Erickson
This has really nothing to do with SQL. What's happening is that the query doesn't think you're specifying a field and it's looking for _text_ which will be defined in your solrconfig file with a "df" parameter for the query handler. That said, the query appears malformed or it's a cut/paste error

Iterating sorted result docs in a custom search component

2017-03-12 Thread alexpusch
I hope this is the right place to ask about custom search components. I'm writing a custom search component. My aim is iterate over the entire result set and do some aggregate computation. In order to implement my algorithm I require to iterate over the result set in the order declared in the sear

q=-id:xxxx in export handler does not work but works ok in select.

2017-03-12 Thread radha krishnan
q=-id: in export handler does not work but works ok in select. Works: http://localhost:8983/solr/bucket4/select?q=id:8733*&rows=1&sort=_version_%20desc&fl=id Does not work: http://localhost:8983/solr/bucket4/export?q=id:8733*&rows=1&sort=_version_%20desc&fl=id looks a bug with solr or am i ma

Re: Simple sql query with where clause doesn't work

2017-03-12 Thread adfel70
Seems like this only happend when the value is not a number curl --data-urlencode 'stmt=select fieldA from collection where field='123'' http://host:port/solr/collection/sql?aggregationMode=facet works. while this one doesnt work: curl --data-urlencode 'stmt=select fieldA from collection where

Simple sql query with where clause doesn't work

2017-03-12 Thread adfel70
Hi I'm trying to play with /sql feature. working with solr 6.4.2 running curl --data-urlencode 'stmt=select fieldA from collection' http://host:port/solr/collection/sql?aggregationMode=facet work fine. running curl --data-urlencode 'stmt=select fieldA from collection where fieldB='value'' http:/