lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Sheldon (JIRA)" <>
Subject [jira] [Commented] (SOLR-1945) Allow @Field annotations in nested classes using DocumentObjectBinder
Date Mon, 18 Apr 2011 20:14:05 GMT


Paul Sheldon commented on SOLR-1945:

I think you are on the right track here with @Field and @FieldObject ideas.  

I'm coming from a compass/lucene environment, getting ready to ditch compass and implement
solr.  compass has a mature set of annotations for things such as @SearchableProperty, @SearchableComponent,
@SearchableDynamicProperty, and so on.  It would be great if solr supported concepts like
these as well!  we have quite a large object tree for marshalling an entity-managed pojo from
the db to the lucene index.  it has a lot of one-to-many and many-to-many relationships (i.e.
collections) that are 'flattened' out during the marshalling process.  this is currently handled
automagically by compass using the simple compass annotations.  in my planning and design
for the conversion to solr, it looks like i'm going to have to code all that 'flattening'
logic myself, fetching and consolidating data from the db to a pojo, and then marshalling
the pojo to solr.

How far do you think your implementation will go?  will it just marshall one-to-one object
graph relationships, or will it also go so far as to handle the one-to-many and many-to-many
(collections) relationships too?

> Allow @Field annotations in nested classes using DocumentObjectBinder
> ---------------------------------------------------------------------
>                 Key: SOLR-1945
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Mark Miller
>            Assignee: Mark Miller
>            Priority: Minor
>             Fix For: Next
>         Attachments: SOLR-1945.patch
> see
> Would be nice to be able to pass an object graph to solrj with @field annotations rather
than just a top level class

This message is automatically generated by JIRA.
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message