Yes I can easily index plain POCO JSON into Solr, as I'm currently using Joerg. Format is slightly different, while in ES you have to specifiy operation, in Solr you need not.
Regarding things about history - I'm not an expert in that... Nevertheless both of them are build upon Lucene which uses BerkeleyDB. This was how I met Solr/ES at first, I was searching for some high-level Berkeley DB other than MongoDB, which is big space glutton... On Tuesday, March 11, 2014 9:04:43 AM UTC+1, Jörg Prante wrote: > > I'm not using JSON with Solr but from what I can see at > https://wiki.apache.org/solr/UpdateJSON there is no difference in what I > said. Solr borrowed all the JSON things from ES. That is, Solr seems not to > accept arbitrary JSON either. So you can index JSON into ES as you would > index it into Solr. > > If you had already data indexed into Solr, this river may help > https://github.com/javanna/elasticsearch-river-solr > > The Solr mock plugin > https://github.com/mattweber/elasticsearch-mocksolrplugin needs some love > for JSON but could also be a valuable start to migrate from Solr. > > Jörg > > > On Tue, Mar 11, 2014 at 7:18 AM, Ondřej Spilka > <spilka...@gmail.com<javascript:> > > wrote: > >> Thanks Joerg, I completely forgot the way of indexing via JSON documents >> I've already done for ES from powershell months ago... >> >> I understand that ES JSON format is very versatile, on the other side, >> Solr compatible option to index plain POCO JSON file which consists only >> from array of objects would be fine in migration from Solr to ES. >> There is no problem while ID property can be specified in schema as like >> as in Solr. >> So when you have schema with ID property you're on the right way and ES >> have to be able to perform index/update on POCO JSON array. >> >> Then I can imagine one have preprocessor converting XML/CSV or whatever >> to collection schema compatible JSON and search engine can be easily chosen >> between ES and Solr. >> It seems like nice idea to me as I'm just a user of search engine... >> >> Ondra >> >> >> On Monday, March 10, 2014 8:19:20 PM UTC+1, Jörg Prante wrote: >>> >>> There is a special ES indexing data model, as you surely already have >>> noted. You can only index a subset of valid JSON into ES. For example, each >>> ES JSON doc must be an object. Arrays must be single-valued, unnested. So, >>> arbitrary source JSON must be transformed, and due to the field/value >>> indexing, there is more than one possible model, which depends on your data >>> domain. >>> >>> XML is also not straightforward to translate. Attributes and values have >>> to be mapped to JSON fields and there is more than one possibility to do so. >>> >>> Another question is how to build identifiers from documents for ES doc >>> _id. >>> >>> In my domain, I transform all my input data (K/V, ISO 2709, JSON, XML) >>> to RDF, create an IRI, and this RDF can be serialized to JSON-LD which fits >>> well into the ES JSON indexing model. YMMV. >>> >>> Jörg >>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "elasticsearch" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to elasticsearc...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/1d480a9f-a043-4de7-a3dc-efa2bea14a17%40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/1d480a9f-a043-4de7-a3dc-efa2bea14a17%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/6d1592b9-8ef1-4371-b572-8ffbe271f1ef%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
