search

srikanthv123 / solrnet

Automatically exported from code.google.com/p/solrnet
0 stars 0 forks source link

Composite document support #49

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Support mapping some fields to a nested document.

See http://www.nabble.com/Composite-POJO-support-td22841854.html

Original issue reported on code.google.com by mauricio...@gmail.com on 2 Apr 2009 at 10:51

GoogleCodeExporter commented 8 years ago 
Issue 100 has been merged into this issue.

Original comment by mauricio...@gmail.com on 15 Apr 2010 at 2:17

GoogleCodeExporter commented 8 years ago

Original comment by mauricio...@gmail.com on 30 May 2010 at 12:24

GoogleCodeExporter commented 8 years ago 
Nabble link above is dead. New link to thread: 
http://lucene.472066.n3.nabble.com/Composite-POJO-support-td496194.html

Original comment by mauricio...@gmail.com on 16 Aug 2010 at 6:45

GoogleCodeExporter commented 8 years ago 
SolrJ JIRA issue about this: https://issues.apache.org/jira/browse/SOLR-1945

Original comment by mauricio...@gmail.com on 8 May 2011 at 4:15

GoogleCodeExporter commented 8 years ago 
Another thread about it (SolrJ) 
http://lucene.472066.n3.nabble.com/Does-SolrJ-support-nested-annotated-beans-td8
68375.html

Original comment by mauricio...@gmail.com on 8 May 2011 at 4:18

GoogleCodeExporter commented 8 years ago 
Workaround: implement ISolrDocumentSerializer<T> / 
ISolrDocumentResponseParser<T> for your document type instead of using SolrNet 
attributes / IReadOnlyMappingManager.

Original comment by mauricio...@gmail.com on 21 Dec 2011 at 2:16

GoogleCodeExporter commented 8 years ago 
How do I use the ISolrDocumentSerializer<T>? I've implemented the interface for 
my class, and use the normal way of adding a document: 
solr.Add(app);

Where 'app' is the class implementing the interface.

Is there anything else I should do?

Original comment by ronald.s...@gmail.com on 14 Sep 2012 at 7:12

GoogleCodeExporter commented 8 years ago 
@ronald.steen register your document serializer in the IoC container. Please 
use the google group if you have further questions.

Original comment by mauricio...@gmail.com on 14 Sep 2012 at 11:34

GoogleCodeExporter commented 8 years ago 
Revisiting this, there seem to be lots of variations to implement this, e.g. 
with a prefix on field names, without prefix, supporting structs... also 
there's the interaction with different implementations of mapping managers. All 
of this would make an ad-hoc solution hard to compose and to reason about.

A cleaner, more composable and generic solution for this would be to provide a 
combinator library to make it easier to implement ISolrDocumentSerializer / 
ISolrDocumentResponseParser.

Original comment by mauricio...@gmail.com on 7 Sep 2013 at 10:41

GoogleCodeExporter commented 8 years ago 
https://groups.google.com/d/msg/solrnet/rqfihOOTsCQ/YnwE_IR6dbYJ

Original comment by mauricio...@gmail.com on 3 Mar 2014 at 6:20