Re: Schema fieldType y-m-d ?!?!

2011-09-17 Thread Erick Erickson
Strings, especially if you sort, facet, etc, will be significantly
more costly in terms
of memory requirements. Doesn't mean you can't, just be aware of the fact...

Best
Erick

On Thu, Sep 15, 2011 at 10:42 AM, stockii stock.jo...@googlemail.com wrote:
 thx =)

 i think i will save this as an string if ranges really works =)

 -
 --- System 
 

 One Server, 12 GB RAM, 2 Solr Instances, 8 Cores,
 1 Core with 45 Million Documents other Cores  200.000

 - Solr1 for Search-Requests - commit every Minute  - 5GB Xmx
 - Solr2 for Update-Request  - delta every Minute - 4GB Xmx
 --
 View this message in context: 
 http://lucene.472066.n3.nabble.com/Schema-fieldType-y-m-d-tp3335359p3339160.html
 Sent from the Solr - User mailing list archive at Nabble.com.



Re: Schema fieldType y-m-d ?!?!

2011-09-15 Thread stockii
thx =) 

i think i will save this as an string if ranges really works =) 

-
--- System 

One Server, 12 GB RAM, 2 Solr Instances, 8 Cores, 
1 Core with 45 Million Documents other Cores  200.000

- Solr1 for Search-Requests - commit every Minute  - 5GB Xmx
- Solr2 for Update-Request  - delta every Minute - 4GB Xmx
--
View this message in context: 
http://lucene.472066.n3.nabble.com/Schema-fieldType-y-m-d-tp3335359p3339160.html
Sent from the Solr - User mailing list archive at Nabble.com.


RE: Schema fieldType y-m-d ?!?!

2011-09-14 Thread Jaeger, Jay - DOT
Just add a bogus 0 timestamp after it when you index it.  That is what we did.  
Dates are not stored or indexed as characters, anyway, so space would not be 
any different one way or the other.

JRJ

-Original Message-
From: stockii [mailto:stock.jo...@googlemail.com] 
Sent: Wednesday, September 14, 2011 4:56 AM
To: solr-user@lucene.apache.org
Subject: Schema fieldType y-m-d ?!?!

is it possible to index a datefield in the format of y-m-d ? i dont need
the timestamp. so i can save me some space.


which ways exists to search with a complex date-filter !? 

-
--- System 

One Server, 12 GB RAM, 2 Solr Instances, 7 Cores, 
1 Core with 31 Million Documents other Cores  100.000

- Solr1 for Search-Requests - commit every Minute  - 5GB Xmx
- Solr2 for Update-Request  - delta every Minute - 4GB Xmx
--
View this message in context: 
http://lucene.472066.n3.nabble.com/Schema-fieldType-y-m-d-tp3335359p3335359.html
Sent from the Solr - User mailing list archive at Nabble.com.


Re: Schema fieldType y-m-d ?!?!

2011-09-14 Thread tamanjit.bin...@yahoo.co.in
What we did was get the date from db, and stored it in a string fieldType in
the format mmdd. It works fine for us, as range query works just fine.

--
View this message in context: 
http://lucene.472066.n3.nabble.com/Schema-fieldType-y-m-d-tp3335359p3336309.html
Sent from the Solr - User mailing list archive at Nabble.com.


Re: Schema fieldType y-m-d ?!?!

2011-09-14 Thread Alexei Martchenko
If you don't need date-specific functions and/or faceting, you can store it
as a int, like 20110914 and parse it in your application

but I don't recommend... as a rule of thumb, dates should be stored as
dates, the millenium bug (Y2K bug) was all about 'saving some space'
remember?