Re: Json Faceting Performance Issues on solr v8.7.0

Ah! that's significant. The latency is likely due to building the OrdinalMap (which maps segment ords to global ords) ... "dvhash" (assuming the relevant fields are not multivalued) will very likely work; "dvhash" doesn't map to global ords, so doesn't need to build the OrdinalMap (which gets built

Re: Json Faceting Performance Issues on solr v8.7.0

> Does this happen on a warm searcher (are subsequent requests with no intervening updates _ever_ fast?)? Subsequent response times very fast if searcher remains open. As a control test, I faceted on the same field that I used in the q param. 1. Start solr 2. Execute q=resultId:x&rows=0 =>

Re: Json Faceting Performance Issues on solr v8.7.0

Apologies, I missed deducing from the request url that you're already talking strictly about single-shard requests (so everything I was suggesting about shards.preference etc. is not applicable). "dvhash" is still worth a try though, esp. with `numFound` being 943 (out of 185 million!). Does this h

Re: Json Faceting Performance Issues on solr v8.7.0

Ok. I'll try that. Meanwhile query on resultId is subsecond response. But the immediate next query for faceting takes 40+secs. The core has 185million docs and 63GB index size. curl 'http://localhost:8983/solr/TestCollection_shard1_replica_t3/query?q=resultId:x&rows=0' { "responseHea

Re: Json Faceting Performance Issues on solr v8.7.0

nalMap creation and array allocation, if either/both of those contribute to the latency you're finding). Michael On Fri, Feb 5, 2021 at 4:42 PM mmb1234 wrote: > Hello, > > I am seeing very slow response from json faceting against a single core > (though core is shard leader in

Json Faceting Performance Issues on solr v8.7.0

Hello, I am seeing very slow response from json faceting against a single core (though core is shard leader in a collection). Fields processId and resultId are non-multivalued, indexed and docvalues string (not text). Soft Commit = 5sec (opensearcher=true) and Hard Commit = 10sec because new

Re: increasing number of threads for faceting in JSON format

tps://youtu.be/qItRilJLj5o > > From: solr-user@lucene.apache.org At: 12/10/20 21:42:19To: > solr-user@lucene.apache.org > Subject: Re: increasing number of threads for faceting in JSON format > > Hi Christine Munendra et al, > > Wow, you dag into the code and checked weather

Re: increasing number of threads for faceting in JSON format

solr-user@lucene.apache.org At: 12/10/20 21:42:19To: solr-user@lucene.apache.org Subject: Re: increasing number of threads for faceting in JSON format Hi Christine Munendra et al, Wow, you dag into the code and checked weather threads are being blown in range and term queries! I wish one day to be

Re: nested facets of query and terms type in JSON format

Jason Gerlowski wrote: > Hey Arturas, > > Can't help you with the secrets of Michael's inspiration (though I'm > also curious :-p). And I'm not sure if there's any equivalent of > facet.threads for JSON Faceting. You're on your own there > unf

Re: increasing number of threads for faceting in JSON format

hristine. > Yeah, JSON facet does not support specifying threads. > > > On Thu, Dec 10, 2020, 11:15 PM Christine Poerschke (BLOOMBERG/ LONDON) < > cpoersc...@bloomberg.net> wrote: > > > Hello Arturas and Munendra! > > > > In the "Currently, JSON facet

Re: nested facets of query and terms type in JSON format

Hey Arturas, Can't help you with the secrets of Michael's inspiration (though I'm also curious :-p). And I'm not sure if there's any equivalent of facet.threads for JSON Faceting. You're on your own there unfortunately. But you (or other readers) might find th

Re: increasing number of threads for faceting in JSON format

Thank you Christine. Yeah, JSON facet does not support specifying threads. On Thu, Dec 10, 2020, 11:15 PM Christine Poerschke (BLOOMBERG/ LONDON) < cpoersc...@bloomberg.net> wrote: > Hello Arturas and Munendra! > > In the "Currently, JSON facets have support for spec

Re: increasing number of threads for faceting in JSON format

Hello Arturas and Munendra! In the "Currently, JSON facets have support for specifying the number of threads." sentence, I wonder if perhaps a "does not" got inadvertently omitted i.e. "Currently, JSON facets does not have support for specifying the number of thread

Re: Can I express this nested query in JSON DSL?

Hi, Mikhail. Shouldn't be a big deal "bool":{ "must":[ "x", {"bool": {"should":["y","z"]}}] } On Tue, Dec 8, 2020 at 6:13 AM Mikhail Edoshin wrote: > Hi, > > I'm more or less new to Solr. I need to run queries that use joins all > over the place. (The idea is to

Can I express this nested query in JSON DSL?

Hi, I'm more or less new to Solr. I need to run queries that use joins all over the place. (The idea is to index database records pretty much as they are and then query them in interesting ways and, most importantly, get the rank. Our dataset is not too large so the performance is great.) I

Re: increasing number of threads for faceting in JSON format

ase the number of threads from one to 20? Cheers, Arturas On Thu, Dec 3, 2020 at 1:54 PM Munendra S N wrote: > Hi, > > Currently, JSON facets have support for specifying the number of threads. > In the above request, the range facet is computed over 2 years with a gap > of 1 hour

Re: nested facets of query and terms type in JSON format

nally grateful for your help! Michael, maybe you happen to know how I can plugin in facet.threads parameter in that JSON body below, so the query uses more threads to compute the answer? I am dying out of curiosity. Cheers, Arturas On Thu, Dec 3, 2020 at 7:59 PM Michael Gibney wrote: > I t

Re: nested facets of query and terms type in JSON format

nge, field:price, ...} but got null , path=/facet", > "code": 400 } } > > If I fire > > { > "query" : "*:*", > "limit" : 0, > > "facet": { > "aip": { "query": "cfname2:ai

Re: nested facets of query and terms type in JSON format

t;: { "type": "range", "field": "t", "sort": { "t": "asc" }, "start": "2018-05-02T17:00:00.000Z", "end": "2020-11-16T

Re: nested facets of query and terms type in JSON format

el On Thu, Dec 3, 2020 at 3:47 AM Arturas Mazeika wrote: > Hi Solr Team, > > I am trying to check how I can formulate facet queries using JSON format. I > can successfully formulate query, range, term queries, as well as nested > term queries. How can I formulate a nested facet q

Re: increasing number of threads for faceting in JSON format

Hi, Currently, JSON facets have support for specifying the number of threads. In the above request, the range facet is computed over 2 years with a gap of 1 hour. By reducing the number of buckets, computation should become much faster Regards, Munendra S N On Thu, Dec 3, 2020 at 1:52 PM

nested facets of query and terms type in JSON format

Hi Solr Team, I am trying to check how I can formulate facet queries using JSON format. I can successfully formulate query, range, term queries, as well as nested term queries. How can I formulate a nested facet query involving "query" as well as "range" formulations? The fol

increasing number of threads for faceting in JSON format

Hi Solr-Users, I am trying to better understand the solr capabilities, how one can formulate queries in JSON format as well as tweak parameters. Currently I have a logs collection (ca 6GB large) with a dozen of attributes running in single server mode (F:\solr_deployment\solr-8.7.0\bin\solr.cmd

Re: Simulate facet.exists for json query facets

cy to be gained by early termination (and avoiding the creation of a DocSet, which at the moment happens unconditionally for every facet query). I'm also thinking about this through the lens of bringing the JSON Facet API to parity with the legacy facet API, fwiw ... On Fri, Oct 30, 2020 at

Re: Simulate facet.exists for json query facets

-). I guess > choosing a different name for the proposed aggregate function would > make sense. I was suggesting it mostly as an alternative to extending > the syntax of JSON Facet "query" facet type, and to say that I think > the implementation of such an aggregate function w

Re: Simulate facet.exists for json query facets

at behaves very differently. So yes, definitely confusing :-). I guess choosing a different name for the proposed aggregate function would make sense. I was suggesting it mostly as an alternative to extending the syntax of JSON Facet "query" facet type, and to say that I think the implemen

Re: Simulate facet.exists for json query facets

@Erick Sorry! I chose a simple example as I wanted to reduce complexity. In detail: * We have distinct contents like tours, offers, events, etc which themselves may be categorized: A tour may be a hiking tour, a mountaineering tour, ... * We have hundreds of customers that want to facet their sear

Re: Simulate facet.exists for json query facets

Separately, and in parallel to Erick's question: indeed I'm not aware of any way to do this currently, but I *can* imagine cases where this would be useful. I have a sense this could be cleanly implemented as a stat facet function (https://lucene.apache.org/solr/guide/8_6/json-facet-api

Re: Simulate facet.exists for json query facets

, what is the problem you’re trying to solve at a high level? Perhaps there’s a better way to figure this out. Best, Erick > On Oct 28, 2020, at 3:48 AM, michael dürr wrote: > > Hi, > > I use json facets of type 'query'. As these queries are pretty slow and I'm > on

Simulate facet.exists for json query facets

Hi, I use json facets of type 'query'. As these queries are pretty slow and I'm only interested in whether there is a match or not, I'd like to restrict the query execution similar to the standard facetting (like with the facet.exists parameter). My simplified query looks som

Re: Help using Noggit for streaming JSON data

, if I do everything correctly, may be able to stream directly to my database. With a *very* complicated CharArr implementation of course :) Thanks, -chris > On Sep 17, 2020, at 12:22, Yonik Seeley wrote: > > See this method: > > /** Reads a JSON string into the output, decod

Re: Help using Noggit for streaming JSON data

See this method: /** Reads a JSON string into the output, decoding any escaped characters. */ public void getString(CharArr output) throws IOException And then the idea is to create a subclass of CharArr to incrementally handle the string that is written to it. You could overload write

Help using Noggit for streaming JSON data

if(c == '"') { eos = true; } else { append to stream } } } But getChar() is not public. The only "documentation" I've really been able to find for Noggit is this post from Yonic back in 2014: http://yonik.com/noggit-json-parser/ It mostly says "Nogg

RE: Solr Logging In JSON Format

Hi, Which version of Solr are you talking about? You should have a log4j.xml or log4j2.xml file in Solr resources that you can customize to your needs. At least that's the way we use to write JSON logs. Maybe there are other options that I don't know. Gaël, De : fidiv...@gmail.c

Solr Logging In JSON Format

Hello, We want to receive Solr logs in DataDog. Configured and all good, but the logs are ugly, not parsed and not really useful. Anyone knows a way to send the logs from Solr in JSON format? Thank you.

Re: Loading JSON docs into Solr with Streaming Expressions?

It's probably time to add JSON loading support to streaming expressions, but nothing yet. This ticket is almost done and paves the way for a suite of parseXYZ functions: https://issues.apache.org/jira/browse/SOLR-14673 Joel Bernstein http://joelsolr.blogspot.com/ On Fri, Jul 24, 2020 at

Loading JSON docs into Solr with Streaming Expressions?

Hey all, I wanted to load some JSON docs into Solr and as I load them, do some manipulations to the documents as they go in. I looked at https://lucene.apache.org/solr/guide/8_6/transforming-and-indexing-custom-json.html <https://lucene.apache.org/solr/guide/8_6/transforming-and-index

Re: [EXTERNAL] Re: JSON Facet with local parameter

ange}%22,%22mincount%22:1,%22limit%22:-1,%22end%22:%22NOW/DAY%22}}&q=*:*&rows=0 "facets": { "count": 14751, "NEW ARRIVALS": { "buckets": [ { "val": "1899-07-13T00:00:00Z", "count": 14750 } ] } } On 7/13/20, 11:12 AM,

Re: JSON Facet with local parameter

The JSON based query APIs (including JSON Faceting) use (and unfortunately subtly different) '${NAME}' syntax for dereferencing variables in the "body" of a JSON data structure... https://lucene.apache.org/solr/guide/8_5/json-request-api.html#parameter-substitution-macro-ex

JSON Facet with local parameter

Is it possible to refer local parameter for Range JSON Facet’s star/end/gap inputs ? I am trying something like below, but it is now working. http://server:8983/solr/kfl/select?arrivalRange=NOW/DAY-10DAYS&json.facet={"NEW ARRIVALS":{"start":$arrivalRange, "sort&q

Re: json faceting - Terms faceting and EnumField

10}}&facet=on&indent=on&wt=json&q=* "Expected numeric field type :ServiceRequestTypeCode{type=ServiceRequestTypeCode,properties=indexed,stored,omitNorms,omitTermFreqAndPositions}" But when I try to do as below it works fine. http://l

json faceting - Terms faceting and EnumField

btype:terms>, field:ServiceRequestTypeCode, limit:10}}&facet=on&indent=on&wt=json&q=* "Expected numeric field type :ServiceRequestTypeCode{type=ServiceRequestTypeCode,properties=indexed,stored,omitNorms,omitTermFreqAndPositions}" But when I try to do as below it

Re: multiple sort terms in json facets sorting

check out the videos on this website TROO.TUBE don't be such a sheep/zombie/loser/NPC. Much love! https://troo.tube/videos/watch/aaa64864-52ee-4201-922f-41300032f219 On Wed, May 13, 2020 at 7:56 AM Saurabh Sharma wrote: > > Hi All, > > I am trying to use two sorting criteria wit

multiple sort terms in json facets sorting

Hi All, I am trying to use two sorting criteria with json facets but found that only one of them is working and other one is not getting honoured. sort:{ sortingScore:desc , x:desc} , Here only sortingScore is being used by solr and parameter x is ignored . Is there any way using which I can use

RE: Possible performance bug - JSON facet - numBuckets:true

"count":603}, { "val":"2019-01-08T01:08:58Z", "count":484}, . . . . "val":"2019-01-26T06:30:33Z", "count":3}]}}} There is 2660 buckets (which is the result of my fix) while

Re: Possible performance bug - JSON facet - numBuckets:true

Hello, Artur. Thanks for your interest. Perhaps, we can amend doc mentioning this effect. In long term it can be optimized by adding a proper condition. Both patches are welcome. On Wed, Feb 12, 2020 at 10:48 PM Rudenko, Artur wrote: > Hello everyone, > I'm am currently investigating a performa

RE: Possible performance bug - JSON facet - numBuckets:true

Guys? Artur Rudenko -Original Message- From: Rudenko, Artur Sent: Saturday, February 15, 2020 12:50 PM To: solr-user@lucene.apache.org Subject: RE: Possible performance bug - JSON facet - numBuckets:true Promoting my question Thanks, Artur Rudenko From: Rudenko, Artur Sent

facet.threads on JSON Facet

Hi, All Is facet.threads available on JSON Facet? If it's available on JSONFacet, how do I specify on request parameters? I'm using facet.threads on JSON Facet like below. I can't confirm any performance difference before-and-after specifying facet.threads=-1 localhost:8983/s

RE: Possible performance bug - JSON facet - numBuckets:true

Promoting my question Thanks, Artur Rudenko From: Rudenko, Artur Sent: Wednesday, February 12, 2020 9:48 PM To: solr-user@lucene.apache.org Subject: Possible performance bug - JSON facet - numBuckets:true Hello everyone, I'm am currently investigating a performance issue in our environmen

Possible performance bug - JSON facet - numBuckets:true

Hello everyone, I'm am currently investigating a performance issue in our environment and it looks like we found a performance bug. Our environment: 20M large PARENT documents and 800M nested small CHILD documents. The system inserts about 400K PARENT documents and 16M CHILD documents per day. (C

Re: JSON from Term Vectors Component

y': 'D10', 'body': { '1': { 'positions': [('position', 92), ('position', 113)] }, '2': { 'positions': [('position', 22), ('position', 413)] } } } } On Thu, Feb 6, 2020 at 12:59 PM Edward Rib

Re: JSON from Term Vectors Component

Python's json lib will convert text as '{"id": 1, "id": 2}' to a dict, that doesn't allow duplicate keys. The solution in this case is to inject your own parsing logic as explained here: https://stackoverflow.com/questions/29321677/python-json-parser-all

Re: JSON from Term Vectors Component

It is one of those things that happens when you don’t have a working group beat on a spec for six months. With an IETF process, I bet JSON would disallow duplicate keys and have comments. It might even have a datetime data type or at least recommend ISO8601 in a string. I was on the Atom

Re: JSON from Term Vectors Component

Well that is interesting, I did not know that! Thanks Walter... https://stackoverflow.com/questions/21832701/does-json-syntax-allow-duplicate-keys-in-an-object I gave it a go in Python (what I'm using) to see what would happen, indeed it gives some odd behavior In [4]: jsonStr = '

Re: JSON from Term Vectors Component

Repeated keys are quite legal in JSON, but many libraries don’t support that. It does look like that data layout could be redesigned to be more portable. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On Feb 6, 2020, at 8:38 AM, Doug Turnb

Re: JSON from Term Vectors Component

Thanks for the tip, The issue is json.nl produces non-standard json with duplicate keys. Solr generates the following, which json lint fails given multiple keys { "positions": { "position": 155, "position": 844, "position": 1726 } } On Thu, Feb

Re: JSON from Term Vectors Component

> > Notice the lists, within lists, within lists. Where the keys are adjacent > items in the list. Is there a reason this isn't a JSON dictionary? > I think this is because of NamedList. Have you tried using json.nl=map as a query parameter for this case? Regards, Munendra S N

JSON from Term Vectors Component

Hi all, I was curious if anyone had any tips on parsing the JSON response of the term vectors component? Or anyway to force it to be more standard JSON? It appears to be very heavily nested and idiosyncratic JSON, such as below. Notice the lists, within lists, within lists. Where the keys are

Re: Solr 8.0 Json Facets are slow - need help

Hello, Kumar. I don't know. 3 / 84 ratio seems reasonable. The only unknown part of the equation was that {!simpleFilter}. Anyway, profiler/sampler might get exact answer. On Fri, Jan 24, 2020 at 8:55 AM kumar gaurav wrote: > HI Mikhail > > Can you please see above debug log and help ? > > Than

Re: Solr 8.0 Json Facets are slow - need help

HI Mikhail Can you please see above debug log and help ? Thanks On Thu, Jan 23, 2020 at 12:05 AM kumar gaurav wrote: > Also > > its not looks like box is slow . because for following query prepare time > is 3 ms but facet time is 84ms on the same box .Don't know why prepare time > was huge fo

Re: Solr 8.0 Json Facets are slow - need help

Also its not looks like box is slow . because for following query prepare time is 3 ms but facet time is 84ms on the same box .Don't know why prepare time was huge for that example :( . debug: { - rawquerystring: "{!parent tag=top which=$pq filters=$child.fq score=max v=$cq}", - queryst

Re: Solr 8.0 Json Facets are slow - need help

> - sub-facet: > > [ > > - > > { > > - processor: "FacetFieldProcessorByArrayDV", > > - elapse: 134, > > - field: "gender_refine", > > - limit: -1, > > - domainSize: 98155, &

Re: Solr 8.0 Json Facets are slow - need help

{ > - processor: "FacetFieldProcessorByArrayDV", > - elapse: 138, > - field: "price_refine", > - limit: -1, > - domainSize: 98155, > - numBuckets: 9, > }, > - > { >

Re: Solr 8.0 Json Facets are slow - need help

nputDocSetSize: 98155, - field: "product", - numBuckets: 1129, }, - { - elapse: 5, - requestedMethod: "not specified", - appliedMetho

Re: Solr 8.0 Json Facets are slow - need help

ge.png] > > > [image: image.png] > > > json facet debug Output:- > > json: > { > >- facet: >{ > - color_refine: > { > - domain: > { > - excludeTags: "rassortment,top,top2,top3,top4,",

Re: Solr 8.0 Json Facets are slow - need help

HI Mikhail Can you please help ? On Tue, Jan 21, 2020 at 7:48 PM kumar gaurav wrote: > Hi Mikhail > > Thanks for your reply . Please help me in this . > > Followings are the screenshot:- > > [image: image.png] > > > [image: image.png] > >

Re: Solr 8.0 Json Facets are slow - need help

Hi Mikhail Thanks for your reply . Please help me in this . Followings are the screenshot:- [image: image.png] [image: image.png] json facet debug Output:- json: { - facet: { - color_refine: { - domain: { - excludeTags: "rassortment,top

Re: Solr 8.0 Json Facets are slow - need help

Hi. Can you share debugQuery=true output? On Tue, Jan 21, 2020 at 1:37 PM kumar gaurav wrote: > HI > > i have a parent child query in which i have used json facet for child > faceting like following. > > qt=/dismax > matchAllQueryRef1=+(+({!query v=$cq})) > sq=+{!luc

Solr 8.0 Json Facets are slow - need help

HI i have a parent child query in which i have used json facet for child faceting like following. qt=/dismax matchAllQueryRef1=+(+({!query v=$cq})) sq=+{!lucene v=$matchAllQueryRef1} q={!parent tag=top which=$pq filters=$child.fq score=max v=$cq} child.fq={!tag=rcolor_refine}filter({!term f

SOLR: when trying to delete all documents, error response body is a html string. How can I get json instead?

Details: https://stackoverflow.com/questions/59337583/solr-when-trying-to-delete-all-documents-error-response-body-is-in-html-string Thank you!

Re: Updates via curl and json not showing in api

On Fri, Dec 13, 2019 at 11:51 AM Shawn Heisey wrote: > > Is there a step I'm missing? > > It appears that you have not executed a commit that opens a new searcher. > > Thanks for explaining this. I turned on commit=true, and everything works as expected. Thanks again, Rhys

Re: Updates via curl and json not showing in api

On 12/13/2019 9:23 AM, rhys J wrote: When I do the following update: curl http://localhost:8983/solr/debt/update -d '[ {"id": "393291-18625", "orig_int_amt":{ "set" : "2.5"}, }]' and then: curl http://localhost:8983/solr/debt/get?id=393291-18625 I see the document is updated via the command l

Updates via curl and json not showing in api

When I do the following update: curl http://localhost:8983/solr/debt/update -d '[ {"id": "393291-18625", "orig_int_amt":{ "set" : "2.5"}, }]' and then: curl http://localhost:8983/solr/debt/get?id=393291-18625 I see the document is updated via the command line. It shows the following: { "doc

Re: JSON Facet doesn't allow date range facets

s I know. > >>> > >>> On 12/12/2019 11:40, Joel Bernstein wrote: > >>>> There is a field type in the schema called pdate: > >>>> > >>>> > >>>> > >>>> This should work for you. > >>>> &

Re: JSON Facet doesn't allow date range facets

ma called pdate: This should work for you. The timeseries Streaming Expression uses the JSON facet API for range faceting and works really well. Joel Bernstein http://joelsolr.blogspot.com/ On Thu, Dec 12, 2019 at 6:28 AM Mel Mason wrote: Hi, I'm trying to have a range face

Re: JSON Facet doesn't allow date range facets

represent that as far as I know. >> >> On 12/12/2019 11:40, Joel Bernstein wrote: >> > There is a field type in the schema called pdate: >> > >> > >> > >> > This should work for you. >> > >> > The timeseries Streaming Expr

Re: JSON Facet doesn't allow date range facets

[2000-05-01 TO 2019-06-02]. > DatePointFields can't represent that as far as I know. > > On 12/12/2019 11:40, Joel Bernstein wrote: > > There is a field type in the schema called pdate: > > > > > > > > This should work for you. > > > > The t

Re: JSON Facet doesn't allow date range facets

uses the JSON facet API for range faceting and works really well. Joel Bernstein http://joelsolr.blogspot.com/ On Thu, Dec 12, 2019 at 6:28 AM Mel Mason wrote: Hi, I'm trying to have a range facet on a field of type solr.DateRangeField. As far as I can tell, this isn't possible

Re: JSON Facet doesn't allow date range facets

There is a field type in the schema called pdate: This should work for you. The timeseries Streaming Expression uses the JSON facet API for range faceting and works really well. Joel Bernstein http://joelsolr.blogspot.com/ On Thu, Dec 12, 2019 at 6:28 AM Mel Mason wrote: > Hi, >

Re: JSON Facet doesn't allow date range facets

Currently, it is not supported yet. Related JIRA - https://issues.apache.org/jira/browse/SOLR-10567 Regards, Munendra S N On Thu, Dec 12, 2019 at 4:58 PM Mel Mason wrote: > Hi, > > I'm trying to have a range facet on a field of type solr.DateRangeField. > As far as I can tell, this isn't poss

JSON Facet doesn't allow date range facets

Hi, I'm trying to have a range facet on a field of type solr.DateRangeField. As far as I can tell, this isn't possible with JSONFacet, only with the old facet system - a quick google turns up several other people with the same problem. When using JSONFacet I get problems with this line of cod

Re: Convert javabin to json

obj = new JavabinCodec().unmarshal(); Utils#writeJson() On Thu, Nov 28, 2019 at 11:54 AM Wei wrote: > > Hi, > > Is there a reliable way to convert solr's javabin response to json format? > We use solrj client with wt=javabin, but want to convert the received > javab

Convert javabin to json

Hi, Is there a reliable way to convert solr's javabin response to json format? We use solrj client with wt=javabin, but want to convert the received javabin response to json for passing to client. We don't want to use wt=json as javabin is more efficient. We tried the noggit jsonu

Re: How to tell which core was used based on Json or XML response from Solr

part then I > would > >> suggest > >> using a client library, not plain curl. There is solarium, for > instance: > >> > >> https://solarium.readthedocs.io/en/stable/ > >> https://github.com/solariumphp/solarium > >> > >> It can use curl under the hood

Re: How to tell which core was used based on Json or XML response from Solr

ttps://github.com/solariumphp/solarium >> >> It can use curl under the hood but you can program your stuff on a higher >> level, >> against an API. >> >> > I am using jquery, so I am using the json package to send and decode the > json that solr sends.

Re: How to tell which core was used based on Json or XML response from Solr

On Mon, Nov 25, 2019 at 10:43 AM David Hastings < hastings.recurs...@gmail.com> wrote: > you missed the part about adding &core= to the query: > &echoParams=all&core=mega > > returns for me: > > "responseHeader":{ > "status":0, > "QTime":0, > "params":{ > "q":"*:*", > "cor

Re: How to tell which core was used based on Json or XML response from Solr

On 11/25/2019 8:30 AM, rhys J wrote: On Mon, Nov 25, 2019 at 2:10 AM Erik Hatcher wrote: add &core=&echoParams=all and the parameter will be in the response header. Erik Thanks. I just tried this, and all I got was this response: http://localhost:8983/solr/dbtr/select?q=debtor_id%3A%2

Re: How to tell which core was used based on Json or XML response from Solr

ve ended up with something that highlights the match in a results table. > It's working, and the client seems happy with that implementation for now. > > > > Why are you using two jQuery files? If you have a web server, you already > > know that which core you queried from.

Re: How to tell which core was used based on Json or XML response from Solr

ueried from. Just convert the Solr JSON response > and add the key "core" and return the modified JSON response. Keep your > front-end query simple - just describe your query. All the other parameters > We are using 2 jquery versions, because this tool is running a tool that has an

Re: How to tell which core was used based on Json or XML response from Solr

der the hood but you can program your stuff on a higher > level, > against an API. > > I am using jquery, so I am using the json package to send and decode the json that solr sends. I hope that makes sense? Thanks for your tip! Our pages are a combo of jquery, javascript, and perl.

Re: How to tell which core was used based on Json or XML response from Solr

On Mon, Nov 25, 2019 at 2:10 AM Erik Hatcher wrote: > add &core=&echoParams=all and the parameter will be in the response > header. > >Erik > Thanks. I just tried this, and all I got was this response: http://localhost:8983/solr/dbtr/select?q=debtor_id%3A%20393291&echoParams=all

Re: How to tell which core was used based on Json or XML response from Solr

s > fired when you type in the search box on www.indiamart.com. > > Why are you using two jQuery files? If you have a web server, you already > know that which core you queried from. Just convert the Solr JSON response > and add the key "core" and return the modified JSON r

Re: How to tell which core was used based on Json or XML response from Solr

add &core=&echoParams=all and the parameter will be in the response header. Erik > On Nov 22, 2019, at 13:27, rhys J wrote: > > I'm implementing an autocomplete search box for Solr. > > I'm using JSON as my response style, and this is the jquery code. &g

Re: How to tell which core was used based on Json or XML response from Solr

that which core you queried from. Just convert the Solr JSON response and add the key "core" and return the modified JSON response. Keep your front-end query simple - just describe your query. All the other parameters can be added on the web server side. Anyways, why do you want to know the

Re: How to tell which core was used based on Json or XML response from Solr

i personally dont like php, but it may just be the easiest way to do what you need assuming you have a basic web server, send your search query to php, and use $_GET or $_POST to read it into a variable: https://www.php.net/manual/en/reserved.variables.get.php then send that to the solr server in

Re: How to tell which core was used based on Json or XML response from Solr

On Fri, Nov 22, 2019 at 1:39 PM David Hastings wrote: > 2 things (maybe 3): > 1. dont have this code facing a client thats not you, otherwise anyone > could view the source and see where the solr server is, which means they > can destroy your index or anything they want. put at the very least a

Re: How to tell which core was used based on Json or XML response from Solr

thing. On Fri, Nov 22, 2019 at 1:27 PM rhys J wrote: > I'm implementing an autocomplete search box for Solr. > > I'm using JSON as my response style, and this is the jquery code. > > > var url='http://10.40.10.14:8983/solr/'+core+'/select/?q='+queryF

How to tell which core was used based on Json or XML response from Solr

I'm implementing an autocomplete search box for Solr. I'm using JSON as my response style, and this is the jquery code. var url='http://10.40.10.14:8983/solr/'+core+'/select/?q='+queryField + query+'&version=2.2&hl=true&start=0&ro

Re: Parts of the Json response to a curl query are arrays, and parts are hashes

On 10/28/2019 9:30 AM, rhys J wrote: Will I break Solr if i change this to default to not multi-valued? If you are only indexing one value in those fields, then setting multiValued to false will not break anything. If an indexing request ever comes in that has more than one value for a fiel

Re: Parts of the Json response to a curl query are arrays, and parts are hashes

I forgot to include the fields created through the API: Thanks, Rhys On Mon, Oct 28, 2019 at 11:30 AM rhys J wrote: > > >> Did you reload the core/collection or restart Solr so the new schema >> would take effect? If it's SolrCloud, did you upload the c

  1   2   3   4   5   6   7   8   9   10   >