Solr document structure for preserving version information

2009-06-05 Thread rossputin 

Hi Guys.

This is a schema design question I suppose.  I would like to store a series
of version elements comprising of two attributes, 'updated' (a date) and
'reason' (just a simple string).  I aim to produce xml based on a search
which would look something like:

document
  name
  version updated=01/04/2009 10:30:00 reason=changes made/
  version updated=02/04/2009 11:10:00 reason=more changes made/
/document

So I realise I could use multiValued fields, but I want to avoid doing
something like:

version01/04/2009 10:30:00|changes made/version (using | or some other
separator)

As I would need to split the field in my code.  This approach does not seem
the best.  Has anyone got an approach they could share ?

Thanks in advance for your help,

 - Ross
-- 
View this message in context: 
http://www.nabble.com/Solr-document-structure-for-preserving-version-information-tp23885262p23885262.html
Sent from the Solr - User mailing list archive at Nabble.com.

Re: Solr document structure for preserving version information

2009-06-05 Thread Otis Gospodnetic 

Would payloads work for this?

Then each version could be a term in a field, and each term (so each version) 
could have the reason stored as its payload.

 Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch



- Original Message 
 From: rossputin rossaj...@yahoo.co.uk
 To: solr-user@lucene.apache.org
 Sent: Friday, June 5, 2009 5:40:18 AM
 Subject: Solr document structure for preserving version information
 
 
 Hi Guys.
 
 This is a schema design question I suppose.  I would like to store a series
 of version elements comprising of two attributes, 'updated' (a date) and
 'reason' (just a simple string).  I aim to produce xml based on a search
 which would look something like:
 
 
   
   
   
 
 
 So I realise I could use multiValued fields, but I want to avoid doing
 something like:
 
 01/04/2009 10:30:00|changes made (using | or some other
 separator)
 
 As I would need to split the field in my code.  This approach does not seem
 the best.  Has anyone got an approach they could share ?
 
 Thanks in advance for your help,
 
 - Ross
 -- 
 View this message in context: 
 http://www.nabble.com/Solr-document-structure-for-preserving-version-information-tp23885262p23885262.html
 Sent from the Solr - User mailing list archive at Nabble.com.