I don't think so, as solr uses a flat index to represent data. I have some
efort towards representing relational data on a flat structure, but until
now I don't have anything too concrete.
My suggestion is: create classes that isolate the parsing strategy, so you
can have dao's that doesn't really
Hi Alex,
Do you think I could then specify an order on the returned fields for
each document, without reordering the fields by parsing the SOLR response ?
Thanks,
Pierre
Alexander Ramos Jardim a écrit :
Hey Pierre,
I don't know if my case helps you, but what I do to keep relational
informat
Hey Pierre,
I don't know if my case helps you, but what I do to keep relational
information is to put the related data all in the same field.
Let me give you an example:
I have a product index. Each product has a list of manufacturer properties,
like dimensions, color, connections supported (usb
Order matters in my application because I'm indexing structured data -
actually, a domain object model (a bit like with Hibernate Search), only
I'm adding parents to children, instead of children to parents. So say I
have Cities and People, with a 1-N relationship between City and People.
I'm i
Yes, this is normal behavior.
Does order matter in your application? Could you explain why?
Order is maintained with multiple values of the same field name,
though - which is important.
Erik
On Aug 17, 2008, at 6:38 PM, Pierre Auslaender wrote:
Hello,
After a Solr query, I alwa
Hello,
After a Solr query, I always get the fields back in alphabetical order,
no matter how I insert them.
Is this the normal behaviour?
This is when adding the document...
ch.tsr.esg.domain.ProgramCollection[id: 1]
collection
Bac à sable
name="collection.url">
