Re: Solr, operating systems and globalization

2007-10-19 Thread Chris Hostetter
: Ah, that is good. So if: : : $ date : Thu Oct 18 12:07:42 PDT 2007 : : Then NOW in Solr will be the absolute date Thu Oct 18 04:07:42 2007 (which is : the current time in UTC)? first off: PDT is only 7 hours off UTC Second: i'm going to get a little bit pedandic... NOW is "now" .. it's an

Re: Solr, operating systems and globalization

2007-10-19 Thread Ken Krugler
On 18-Oct-07, at 11:43 AM, Chris Hostetter wrote: : This is easy--I always convert dates to UTC. Doubly important since several : of our servers operate in different timezones. : : Less easy is changing Solr's interpretation of NOW in DateMath to be UTC. : What is the correct way to go about t

Re: Solr, operating systems and globalization

2007-10-18 Thread Mike Klaas
On 18-Oct-07, at 11:43 AM, Chris Hostetter wrote: : This is easy--I always convert dates to UTC. Doubly important since several : of our servers operate in different timezones. : : Less easy is changing Solr's interpretation of NOW in DateMath to be UTC. : What is the correct way to go abo

Re: Solr, operating systems and globalization

2007-10-18 Thread Chris Hostetter
: This is easy--I always convert dates to UTC. Doubly important since several : of our servers operate in different timezones. : : Less easy is changing Solr's interpretation of NOW in DateMath to be UTC. : What is the correct way to go about this? You lost me there ... "Dates" in java have no c

Re: Solr, operating systems and globalization

2007-10-18 Thread Mike Klaas
On 17-Oct-07, at 1:52 PM, Chris Hostetter wrote: : However, SolrSharp culture settings should be reflective and consistent with : the solr server instance's culture. This leads to my question: does Solr : control its culture & language settings through the various language : components th

Re: Solr, operating systems and globalization

2007-10-18 Thread Jeff Rodenburg
OK, this simplifies things greatly. For C#, the proper culture setting for interaction with Solr should be Invariant. Basically, the primary requirement for Solrsharp is to be "culturally-consistent" with the targeted Solr server to ensure proper data-type formatting. Since Solr is culturally-ag

Re: Solr, operating systems and globalization

2007-10-17 Thread Chris Hostetter
: This is exactly the scenario. Ideally what I'd like to achieve is for : Solrsharp to discover the culture settings from the targeted Solr instance : and set the client in appropriate position. well ... my point is there shouldn't be any cultural settings on the "targeted" Solr server that the

Re: Solr, operating systems and globalization

2007-10-17 Thread Jeff Rodenburg
Thanks for the comments Hoss. More notes embedded below... On 10/17/07, Chris Hostetter <[EMAIL PROTECTED]> wrote: > > > : However, SolrSharp culture settings should be reflective and consistent > with > : the solr server instance's culture. This leads to my question: does > Solr > : control its

Re: Solr, operating systems and globalization

2007-10-17 Thread Chris Hostetter
: However, SolrSharp culture settings should be reflective and consistent with : the solr server instance's culture. This leads to my question: does Solr : control its culture & language settings through the various language : components that can be incorporated, or does the underlying OS have a

Solr, operating systems and globalization

2007-10-12 Thread Jeff Rodenburg
We discovered and verified an issue in SolrSharp whereby indexing and searching can be disrupted without taking Windows globalization & culture settings into consideration. For example, European cultures affect numeric and date values differently from US/English cultures. The resolution for this