Thanks a lot for your for your help, Joel.
Just wondering, why does "export" have such limitations? It uses the same
query handler with "select", isn't it?
2014-12-31 10:28 GMT+08:00 Joel Bernstein :
> For the initial release only JSON output format is supported with the
> /export feature. Also t
For the initial release only JSON output format is supported with the
/export feature. Also there is no built-in distributed support yet. Both of
these features are likely to follow in future releases.
For the initial release you'll need a client that can handle the JSON
format and distributed log
Hi, Joel
Thanks for your reply.
It seems that the weird export results is because that I removed the "xsort" invariant of the export request handler in the default
sorlconfig.xml to get csv-format output.
I don't quite understand the meaning of "xsort", but I removed it because I
always get json r
Hi Sandy,
I pulled Solr 4.10.3 to see if I could recreate the issue you are seeing
with export and I wasn't able to recreate the bug you are seeing. For
example the following query:
http://localhost:8983/solr/collection1/export?q=join_i:[50 TO
500010]&wt=json&indent=true&sort=join_i+asc&fl=jo
Hi Sandy,
The export handler should only return documents in JSON format. The results
in your second example are in XML for format so something looks to be wrong
in the configuration. Can you post what your solrconfig looks like?
Joel
Joel Bernstein
Search Engineer at Heliosearch
On Fri, Dec 26
I think you missed a very important part of Jack's reply:
bq: I notice that you don't have distrib=false on your select, which
would make your select be from all nodes, while export would only be
docs from the specific node you sent the request to.
And from the Reference Guide on export
bq: The
Hi,
Do you have any custom solr components deployed? May be custom response writer?
Ahmet
On Friday, December 26, 2014 3:26 PM, Sandy Ding
wrote:
Hi, Ahmet,
I use libuuid for unique id and I guess there shouldn't be duplicate ids.
Also, the results are not just incomplete, they are screwed
Hi, Ahmet,
I use libuuid for unique id and I guess there shouldn't be duplicate ids.
Also, the results are not just incomplete, they are screwed.
2014-12-26 20:19 GMT+08:00 Ahmet Arslan :
> Hi,
>
> Two different things :
>
> If you have unique key defined document with same id override within a
Thanks for your reply, Jack.
The export result sets are incorrect in the sense that results totally
don't match the query.
For example, when I query age=20(age is int type), the results contains
age=14, 22...
curl "http://localhost:8983/solr/pa_info/export?q=age:20&fl=id,age"; will
get the follo
Hi,
Two different things :
If you have unique key defined document with same id override within a single
shard.
Plus, uniqueIDs expected to be unique across shards.
Ahmet
On Friday, December 26, 2014 11:00 AM, Sandy Ding
wrote:
Hi, all
I've recently set up a solr cluster and found that "
You neglected to tell us specifically in what way the export result is
incorrect. Is some of the data missing, duplicated, garbled, or... what?
Provide an example and be specific about what you think is "wrong" in the
results.
Have you modified the default solrconfig file?
I notice that you don't
Hi, all
I've recently set up a solr cluster and found that "export" returns
different results from "select".
And I confirmed that the "export" results are wrong by manually query the
results.
Even simple queries as follows will get different results:
curl "http://localhost:8983/solr/pa_info/selec
12 matches
Mail list logo
