Re: Facing issue while transforming and indexing custom JSON
Do you have _src_ field declared in schema? It is just a non-indexed string:
https://github.com/apache/lucene-solr/blob/releases/lucene-solr/7.5.0/solr/server/solr/configsets/sample_techproducts_configs/conf/managed-schema#L169
Regards,
Alex.
On Mon, 31 Dec 2018 at 04:35, Shubhangi Shinde
wrote:
>
> Hi Team,
>
> I am waiting for your feedback. Any update on this issue?
>
> On Fri, Dec 28, 2018 at 12:11 PM Shubhangi Shinde <
> shubhangi.shi...@iauro.com> wrote:
>
> > Hi Team,
> >
> > I am using Apache Solr. I went through the below link 'https://lucene.
> > apache.org/solr
> > /guide/7_5/transforming-and-indexing-custom-json.html#setting-json-defaults'
> > for transforming and indexing custom JSON and added the code in one of the
> > core to upload a multilevel JSON. It is throwing the below error. I spent
> > so much time to solve this error but no luck. The error is,
> >
> > {
> > "responseHeader":{
> > "status":400,
> > "QTime":93},
> > "error":{
> > "metadata":[
> > "error-class","org.apache.solr.common.SolrException",
> > "root-error-class","org.apache.solr.common.SolrException"],
> > "msg":"ERROR: [doc=5b62d25] unknown field '_src_'",
> > "code":400}}
> >
> > I added the below code in my solrconfig.xml file. Please check,
> >
> >
> >
> >
> > _src_
> >
> > true
> >
> > text
> >
> >
> >
> > Please check the issue on stack overflow on the below link,
> > https://stackoverflow.com/questions/53775064/apache-solr
> > -error-unknown-field-src
> >
> > Please let me know if you want some more information about this. Thanks in
> > advance.
> >
> > --
> >
> > *Shubhangi Shinde*
> > Sr. Software Engineer, iauro Systems Pvt. Ltd.
> > 020-64008585 | shubhangi.shi...@iauro.com | www.iauro.com
> > <http://goo.gl/CcgMgN>
> > <http://www.linkedin.com/company/iauro-systems-pvt-ltd>
> > <http://twitter.com/iauro> <http://www.facebook.com/iauro>
> >
>
>
> --
>
> *Shubhangi Shinde*
> Sr. Software Engineer, iauro Systems Pvt. Ltd.
> 020-64008585 | shubhangi.shi...@iauro.com | www.iauro.com
> <http://goo.gl/CcgMgN>
> <http://www.linkedin.com/company/iauro-systems-pvt-ltd>
> <http://twitter.com/iauro> <http://www.facebook.com/iauro>
Re: Facing issue while transforming and indexing custom JSON
Hi Team,
I am waiting for your feedback. Any update on this issue?
On Fri, Dec 28, 2018 at 12:11 PM Shubhangi Shinde <
shubhangi.shi...@iauro.com> wrote:
> Hi Team,
>
> I am using Apache Solr. I went through the below link 'https://lucene.
> apache.org/solr
> /guide/7_5/transforming-and-indexing-custom-json.html#setting-json-defaults'
> for transforming and indexing custom JSON and added the code in one of the
> core to upload a multilevel JSON. It is throwing the below error. I spent
> so much time to solve this error but no luck. The error is,
>
> {
> "responseHeader":{
> "status":400,
> "QTime":93},
> "error":{
> "metadata":[
> "error-class","org.apache.solr.common.SolrException",
> "root-error-class","org.apache.solr.common.SolrException"],
> "msg":"ERROR: [doc=5b62d25] unknown field '_src_'",
> "code":400}}
>
> I added the below code in my solrconfig.xml file. Please check,
>
>
>
>
> _src_
>
> true
>
> text
>
>
>
> Please check the issue on stack overflow on the below link,
> https://stackoverflow.com/questions/53775064/apache-solr
> -error-unknown-field-src
>
> Please let me know if you want some more information about this. Thanks in
> advance.
>
> --
>
> *Shubhangi Shinde*
> Sr. Software Engineer, iauro Systems Pvt. Ltd.
> 020-64008585 | shubhangi.shi...@iauro.com | www.iauro.com
> <http://goo.gl/CcgMgN>
> <http://www.linkedin.com/company/iauro-systems-pvt-ltd>
> <http://twitter.com/iauro> <http://www.facebook.com/iauro>
>
--
*Shubhangi Shinde*
Sr. Software Engineer, iauro Systems Pvt. Ltd.
020-64008585 | shubhangi.shi...@iauro.com | www.iauro.com
<http://goo.gl/CcgMgN>
<http://www.linkedin.com/company/iauro-systems-pvt-ltd>
<http://twitter.com/iauro> <http://www.facebook.com/iauro>
Re: Custom JSON facet functions
On Tue, Feb 9, 2016 at 10:02 AM, Markus Jelsma wrote: > Nice! Are the aggregations also going to be pluggable? Reading the ticket, i > would assume it is going to be pluggable. Yep. -Yonik > Thanks, > Markus > > -Original message- >> From:Yonik Seeley >> Sent: Tuesday 9th February 2016 15:25 >> To: solr-user@lucene.apache.org >> Subject: Re: Custom JSON facet functions >> >> On Tue, Feb 9, 2016 at 7:10 AM, Markus Jelsma >> wrote: >> > Hi - i must have missing something but is it possible to declare custom >> > JSON facet functions in solrconfig.xml? Just like we would do with request >> > handlers or search components? >> >> Yes, but it will probably change: >> https://issues.apache.org/jira/browse/SOLR-7447 >> >> So currently, you would register a facet function just like a custom >> function (value source), >> but just put "_agg" at the end of the name and implement AggValueSource. >> So for example, the "sum" facet function is registered as "sum_agg" >> and implements AggValueSource (the class is SumAgg) >> >> So if you utilize this, just realize that the mechanism and interfaces >> are experimental and subject to change (and probably will change at >> some point for this in particular). >> >> -Yonik >>
RE: Custom JSON facet functions
Nice! Are the aggregations also going to be pluggable? Reading the ticket, i would assume it is going to be pluggable. Thanks, Markus -Original message- > From:Yonik Seeley > Sent: Tuesday 9th February 2016 15:25 > To: solr-user@lucene.apache.org > Subject: Re: Custom JSON facet functions > > On Tue, Feb 9, 2016 at 7:10 AM, Markus Jelsma > wrote: > > Hi - i must have missing something but is it possible to declare custom > > JSON facet functions in solrconfig.xml? Just like we would do with request > > handlers or search components? > > Yes, but it will probably change: > https://issues.apache.org/jira/browse/SOLR-7447 > > So currently, you would register a facet function just like a custom > function (value source), > but just put "_agg" at the end of the name and implement AggValueSource. > So for example, the "sum" facet function is registered as "sum_agg" > and implements AggValueSource (the class is SumAgg) > > So if you utilize this, just realize that the mechanism and interfaces > are experimental and subject to change (and probably will change at > some point for this in particular). > > -Yonik >
Re: Custom JSON facet functions
On Tue, Feb 9, 2016 at 7:10 AM, Markus Jelsma wrote: > Hi - i must have missing something but is it possible to declare custom JSON > facet functions in solrconfig.xml? Just like we would do with request > handlers or search components? Yes, but it will probably change: https://issues.apache.org/jira/browse/SOLR-7447 So currently, you would register a facet function just like a custom function (value source), but just put "_agg" at the end of the name and implement AggValueSource. So for example, the "sum" facet function is registered as "sum_agg" and implements AggValueSource (the class is SumAgg) So if you utilize this, just realize that the mechanism and interfaces are experimental and subject to change (and probably will change at some point for this in particular). -Yonik
Custom JSON facet functions
Hi - i must have missing something but is it possible to declare custom JSON facet functions in solrconfig.xml? Just like we would do with request handlers or search components? Thanks, Markus
Re: solr output in custom json format
I think what ideally is needed here is an implementation for this open issue: <https://issues.apache.org/jira/browse/SOLR-3479 <https://issues.apache.org/jira/browse/SOLR-3479>> — Erik Hatcher, Senior Solutions Architect http://www.lucidworks.com <http://www.lucidworks.com/> > On Feb 18, 2015, at 12:51 PM, meena.sri...@mathworks.com wrote: > > Sorry I was missing the actual part that is without parsing the json output. > I was looking in to Solrj > QueryReponse.getBeans(Syndrome.class) , but how do I embed highlighting > snippet inside each of the Syndrome object itself. > > Thanks > meena > > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/solr-output-in-custom-json-format-tp4187200p4187202.html > Sent from the Solr - User mailing list archive at Nabble.com.
Re: solr output in custom json format
Sorry I was missing the actual part that is without parsing the json output. I was looking in to Solrj QueryReponse.getBeans(Syndrome.class) , but how do I embed highlighting snippet inside each of the Syndrome object itself. Thanks meena -- View this message in context: http://lucene.472066.n3.nabble.com/solr-output-in-custom-json-format-tp4187200p4187202.html Sent from the Solr - User mailing list archive at Nabble.com.
solr output in custom json format
I need to create custom json format of solr output for a specific UI. I was wondering if there is a way to embed "highlighting" portion inside docs itself. Thanks Meena -- View this message in context: http://lucene.472066.n3.nabble.com/solr-output-in-custom-json-format-tp4187200.html Sent from the Solr - User mailing list archive at Nabble.com.
Indexing Custom JSON with SolrJ
Does SolrJ have anything that allows you to change the update handler and add something besides a SolrInputDocument? I'm trying to figure out how to add JSON documents using the custom JSON update handler (http://lucidworks.com/blog/indexing-custom-json-data/), but doing it through SolrJ in order to leverage CloudSolrServer. Thanks, Bryan
Re: Custom JSON
Awesome. How long did it take? Personal: http://www.outerthoughts.com/ and @arafalov Solr resources and newsletter: http://www.solr-start.com/ and @solrstart Solr popularizers community: https://www.linkedin.com/groups?gid=6713853 On 20 October 2014 03:59, Noble Paul wrote: > check https://issues.apache.org/jira/browse/SOLR-6633 > > On Fri, Oct 17, 2014 at 5:35 PM, Alexandre Rafalovitch > wrote: > >> I wonder how hard it would be to write an URP to just copy JSON from the >> request into a store-only field? >> >> Regards, >> Alex >> On 17/10/2014 1:21 am, "Noble Paul" wrote: >> >> > The original json is is not stored the fields are extracted and the data >> is >> > thrown away >> > >> > On Fri, Oct 17, 2014 at 1:18 AM, Scott Dawson >> > wrote: >> > >> > > Noble, >> > > Thanks. You're right. I had some things incorrectly configured but now >> I >> > > can put structured JSON into Solr using the out-of-the-box >> > solrconfig.xml. >> > > >> > > One additional question: Is there any way to query Solr and receive the >> > > original structured JSON document in response? Or does the flattening >> > > process that happens during indexing obliterate the original structure >> > with >> > > no way to reconstruct it? >> > > >> > > Thanks again, >> > > Scott >> > > >> > > On Thu, Oct 16, 2014 at 2:10 PM, Noble Paul >> > wrote: >> > > >> > > > The end point /update/json/docs is enabled implicitly in Solr >> > > irrespective >> > > > of the solrconfig.xml >> > > > In schemaless the fields are created automatically by solr. >> > > > >> > > > If you have all the fields created in your schema.xml it will work . >> > > > >> > > > if you need an id field please use a copy field to create one >> > > > >> > > > --Noble >> > > > >> > > > On Thu, Oct 16, 2014 at 8:42 PM, Scott Dawson > > >> > > > wrote: >> > > > >> > > > > Hello, >> > > > > I'm trying to use the new custom JSON feature described in >> > > > > https://issues.apache.org/jira/browse/SOLR-6304. I'm running Solr >> > > > 4.10.1. >> > > > > It seems that the new feature, or more specifically, the >> > > > /update/json/docs >> > > > > endpoint is not enabled out-of-the-box except in the schema-less >> > > example. >> > > > > Is there some dependence of the feature on schemaless mode? I've >> > tried >> > > > > pulling the endpoint definition and related pieces of the >> > > > > example-schemaless solrconfig.xml and adding those to the >> "standard" >> > > > > solrconfig.xml in the main example but I've run into a cascade of >> > > issues. >> > > > > Right now I'm getting a "This IndexSchema is not mutable" exception >> > > when >> > > > I >> > > > > try to post to the /update/json/docs endpoint. >> > > > > >> > > > > My real question is -- what's the easiest way to get this feature >> up >> > > and >> > > > > running quickly and is this documented somewhere? I'm trying to do >> a >> > > > quick >> > > > > proof-of-concept to verify that we can move from our current flat >> > JSON >> > > > > ingestion to a more natural use of structured JSON. >> > > > > >> > > > > Thanks, >> > > > > Scott Dawson >> > > > > >> > > > >> > > > >> > > > >> > > > -- >> > > > - >> > > > Noble Paul >> > > > >> > > >> > >> > >> > >> > -- >> > - >> > Noble Paul >> > >> > > > > -- > - > Noble Paul
Re: Custom JSON
check https://issues.apache.org/jira/browse/SOLR-6633 On Fri, Oct 17, 2014 at 5:35 PM, Alexandre Rafalovitch wrote: > I wonder how hard it would be to write an URP to just copy JSON from the > request into a store-only field? > > Regards, > Alex > On 17/10/2014 1:21 am, "Noble Paul" wrote: > > > The original json is is not stored the fields are extracted and the data > is > > thrown away > > > > On Fri, Oct 17, 2014 at 1:18 AM, Scott Dawson > > wrote: > > > > > Noble, > > > Thanks. You're right. I had some things incorrectly configured but now > I > > > can put structured JSON into Solr using the out-of-the-box > > solrconfig.xml. > > > > > > One additional question: Is there any way to query Solr and receive the > > > original structured JSON document in response? Or does the flattening > > > process that happens during indexing obliterate the original structure > > with > > > no way to reconstruct it? > > > > > > Thanks again, > > > Scott > > > > > > On Thu, Oct 16, 2014 at 2:10 PM, Noble Paul > > wrote: > > > > > > > The end point /update/json/docs is enabled implicitly in Solr > > > irrespective > > > > of the solrconfig.xml > > > > In schemaless the fields are created automatically by solr. > > > > > > > > If you have all the fields created in your schema.xml it will work . > > > > > > > > if you need an id field please use a copy field to create one > > > > > > > > --Noble > > > > > > > > On Thu, Oct 16, 2014 at 8:42 PM, Scott Dawson > > > > > wrote: > > > > > > > > > Hello, > > > > > I'm trying to use the new custom JSON feature described in > > > > > https://issues.apache.org/jira/browse/SOLR-6304. I'm running Solr > > > > 4.10.1. > > > > > It seems that the new feature, or more specifically, the > > > > /update/json/docs > > > > > endpoint is not enabled out-of-the-box except in the schema-less > > > example. > > > > > Is there some dependence of the feature on schemaless mode? I've > > tried > > > > > pulling the endpoint definition and related pieces of the > > > > > example-schemaless solrconfig.xml and adding those to the > "standard" > > > > > solrconfig.xml in the main example but I've run into a cascade of > > > issues. > > > > > Right now I'm getting a "This IndexSchema is not mutable" exception > > > when > > > > I > > > > > try to post to the /update/json/docs endpoint. > > > > > > > > > > My real question is -- what's the easiest way to get this feature > up > > > and > > > > > running quickly and is this documented somewhere? I'm trying to do > a > > > > quick > > > > > proof-of-concept to verify that we can move from our current flat > > JSON > > > > > ingestion to a more natural use of structured JSON. > > > > > > > > > > Thanks, > > > > > Scott Dawson > > > > > > > > > > > > > > > > > > > > > -- > > > > - > > > > Noble Paul > > > > > > > > > > > > > > > -- > > - > > Noble Paul > > > -- - Noble Paul
Re: Custom JSON
I wonder how hard it would be to write an URP to just copy JSON from the request into a store-only field? Regards, Alex On 17/10/2014 1:21 am, "Noble Paul" wrote: > The original json is is not stored the fields are extracted and the data is > thrown away > > On Fri, Oct 17, 2014 at 1:18 AM, Scott Dawson > wrote: > > > Noble, > > Thanks. You're right. I had some things incorrectly configured but now I > > can put structured JSON into Solr using the out-of-the-box > solrconfig.xml. > > > > One additional question: Is there any way to query Solr and receive the > > original structured JSON document in response? Or does the flattening > > process that happens during indexing obliterate the original structure > with > > no way to reconstruct it? > > > > Thanks again, > > Scott > > > > On Thu, Oct 16, 2014 at 2:10 PM, Noble Paul > wrote: > > > > > The end point /update/json/docs is enabled implicitly in Solr > > irrespective > > > of the solrconfig.xml > > > In schemaless the fields are created automatically by solr. > > > > > > If you have all the fields created in your schema.xml it will work . > > > > > > if you need an id field please use a copy field to create one > > > > > > --Noble > > > > > > On Thu, Oct 16, 2014 at 8:42 PM, Scott Dawson > > > wrote: > > > > > > > Hello, > > > > I'm trying to use the new custom JSON feature described in > > > > https://issues.apache.org/jira/browse/SOLR-6304. I'm running Solr > > > 4.10.1. > > > > It seems that the new feature, or more specifically, the > > > /update/json/docs > > > > endpoint is not enabled out-of-the-box except in the schema-less > > example. > > > > Is there some dependence of the feature on schemaless mode? I've > tried > > > > pulling the endpoint definition and related pieces of the > > > > example-schemaless solrconfig.xml and adding those to the "standard" > > > > solrconfig.xml in the main example but I've run into a cascade of > > issues. > > > > Right now I'm getting a "This IndexSchema is not mutable" exception > > when > > > I > > > > try to post to the /update/json/docs endpoint. > > > > > > > > My real question is -- what's the easiest way to get this feature up > > and > > > > running quickly and is this documented somewhere? I'm trying to do a > > > quick > > > > proof-of-concept to verify that we can move from our current flat > JSON > > > > ingestion to a more natural use of structured JSON. > > > > > > > > Thanks, > > > > Scott Dawson > > > > > > > > > > > > > > > > -- > > > - > > > Noble Paul > > > > > > > > > -- > - > Noble Paul >
Re: Custom JSON
The original json is is not stored the fields are extracted and the data is thrown away On Fri, Oct 17, 2014 at 1:18 AM, Scott Dawson wrote: > Noble, > Thanks. You're right. I had some things incorrectly configured but now I > can put structured JSON into Solr using the out-of-the-box solrconfig.xml. > > One additional question: Is there any way to query Solr and receive the > original structured JSON document in response? Or does the flattening > process that happens during indexing obliterate the original structure with > no way to reconstruct it? > > Thanks again, > Scott > > On Thu, Oct 16, 2014 at 2:10 PM, Noble Paul wrote: > > > The end point /update/json/docs is enabled implicitly in Solr > irrespective > > of the solrconfig.xml > > In schemaless the fields are created automatically by solr. > > > > If you have all the fields created in your schema.xml it will work . > > > > if you need an id field please use a copy field to create one > > > > --Noble > > > > On Thu, Oct 16, 2014 at 8:42 PM, Scott Dawson > > wrote: > > > > > Hello, > > > I'm trying to use the new custom JSON feature described in > > > https://issues.apache.org/jira/browse/SOLR-6304. I'm running Solr > > 4.10.1. > > > It seems that the new feature, or more specifically, the > > /update/json/docs > > > endpoint is not enabled out-of-the-box except in the schema-less > example. > > > Is there some dependence of the feature on schemaless mode? I've tried > > > pulling the endpoint definition and related pieces of the > > > example-schemaless solrconfig.xml and adding those to the "standard" > > > solrconfig.xml in the main example but I've run into a cascade of > issues. > > > Right now I'm getting a "This IndexSchema is not mutable" exception > when > > I > > > try to post to the /update/json/docs endpoint. > > > > > > My real question is -- what's the easiest way to get this feature up > and > > > running quickly and is this documented somewhere? I'm trying to do a > > quick > > > proof-of-concept to verify that we can move from our current flat JSON > > > ingestion to a more natural use of structured JSON. > > > > > > Thanks, > > > Scott Dawson > > > > > > > > > > > -- > > - > > Noble Paul > > > -- - Noble Paul
Re: Custom JSON
Noble, Thanks. You're right. I had some things incorrectly configured but now I can put structured JSON into Solr using the out-of-the-box solrconfig.xml. One additional question: Is there any way to query Solr and receive the original structured JSON document in response? Or does the flattening process that happens during indexing obliterate the original structure with no way to reconstruct it? Thanks again, Scott On Thu, Oct 16, 2014 at 2:10 PM, Noble Paul wrote: > The end point /update/json/docs is enabled implicitly in Solr irrespective > of the solrconfig.xml > In schemaless the fields are created automatically by solr. > > If you have all the fields created in your schema.xml it will work . > > if you need an id field please use a copy field to create one > > --Noble > > On Thu, Oct 16, 2014 at 8:42 PM, Scott Dawson > wrote: > > > Hello, > > I'm trying to use the new custom JSON feature described in > > https://issues.apache.org/jira/browse/SOLR-6304. I'm running Solr > 4.10.1. > > It seems that the new feature, or more specifically, the > /update/json/docs > > endpoint is not enabled out-of-the-box except in the schema-less example. > > Is there some dependence of the feature on schemaless mode? I've tried > > pulling the endpoint definition and related pieces of the > > example-schemaless solrconfig.xml and adding those to the "standard" > > solrconfig.xml in the main example but I've run into a cascade of issues. > > Right now I'm getting a "This IndexSchema is not mutable" exception when > I > > try to post to the /update/json/docs endpoint. > > > > My real question is -- what's the easiest way to get this feature up and > > running quickly and is this documented somewhere? I'm trying to do a > quick > > proof-of-concept to verify that we can move from our current flat JSON > > ingestion to a more natural use of structured JSON. > > > > Thanks, > > Scott Dawson > > > > > > -- > - > Noble Paul >
Re: Custom JSON
The end point /update/json/docs is enabled implicitly in Solr irrespective of the solrconfig.xml In schemaless the fields are created automatically by solr. If you have all the fields created in your schema.xml it will work . if you need an id field please use a copy field to create one --Noble On Thu, Oct 16, 2014 at 8:42 PM, Scott Dawson wrote: > Hello, > I'm trying to use the new custom JSON feature described in > https://issues.apache.org/jira/browse/SOLR-6304. I'm running Solr 4.10.1. > It seems that the new feature, or more specifically, the /update/json/docs > endpoint is not enabled out-of-the-box except in the schema-less example. > Is there some dependence of the feature on schemaless mode? I've tried > pulling the endpoint definition and related pieces of the > example-schemaless solrconfig.xml and adding those to the "standard" > solrconfig.xml in the main example but I've run into a cascade of issues. > Right now I'm getting a "This IndexSchema is not mutable" exception when I > try to post to the /update/json/docs endpoint. > > My real question is -- what's the easiest way to get this feature up and > running quickly and is this documented somewhere? I'm trying to do a quick > proof-of-concept to verify that we can move from our current flat JSON > ingestion to a more natural use of structured JSON. > > Thanks, > Scott Dawson > -- - Noble Paul
Custom JSON
Hello, I'm trying to use the new custom JSON feature described in https://issues.apache.org/jira/browse/SOLR-6304. I'm running Solr 4.10.1. It seems that the new feature, or more specifically, the /update/json/docs endpoint is not enabled out-of-the-box except in the schema-less example. Is there some dependence of the feature on schemaless mode? I've tried pulling the endpoint definition and related pieces of the example-schemaless solrconfig.xml and adding those to the "standard" solrconfig.xml in the main example but I've run into a cascade of issues. Right now I'm getting a "This IndexSchema is not mutable" exception when I try to post to the /update/json/docs endpoint. My real question is -- what's the easiest way to get this feature up and running quickly and is this documented somewhere? I'm trying to do a quick proof-of-concept to verify that we can move from our current flat JSON ingestion to a more natural use of structured JSON. Thanks, Scott Dawson
