Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: pass (nike.apache.org: domain of pranny@gmail.com designates
 209.85.215.48 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAM6QAw200CbuN6TNaVugWnfmhVwWkxkW-GK2oKL6c6Nov4bvkQ@mail.gmail.com>
References: 
 <CAPp-OAu2U6YQQiv9zccskorv5rnYZQ1oYQrcBWv=dOFcF_NPQg@mail.gmail.com>
 <alpine.DEB.2.02.1209061725310.17122@frisbee>
 <CAPp-OAurS_U5oVS86ekA2kdWjmZBhnG07K6B=togCk5h-N5dqQ@mail.gmail.com>
 <504A6B36.4040304@elyograg.org>
 <CAM6QAw200CbuN6TNaVugWnfmhVwWkxkW-GK2oKL6c6Nov4bvkQ@mail.gmail.com>
From: Pranav Prakash <pranny@gmail.com>
Date: Mon, 10 Sep 2012 15:10:01 +0530
Message-ID: 
 <CAM6QAw1+BbFEtLVtdnY6wc5=hJd8T3guOHzCHcDr_oW7SsyX_g@mail.gmail.com>
Subject: Re: Importing of unix date format from mysql database and dates of
 format 'Thu, 06 Sep 2012 22:32:33 +0000' in Solr 4.0
To: solr-user@lucene.apache.org
Content-Type: multipart/alternative; boundary=e0cb4efe35861e001004c955bf7d

--e0cb4efe35861e001004c955bf7d
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

The character is actually  - =93 and not "


*Pranav Prakash*

"temet nosce"


On Mon, Sep 10, 2012 at 2:45 PM, Pranav Prakash <pranny@gmail.com> wrote:

> I am experiencing similar problem related to encoding. In my case, the
> char like " (double quote)
> is also garbaled.
>
> I believe this is because the encoding in my MySQL table is latin1 and in
> the JDBC it is being specified as UTF-8. Is there a way to specify latin1
> charset in JDBC? probably that would resolve this.
>
>
> *Pranav Prakash*
>
> "temet nosce"
>
>
>
>
> On Sat, Sep 8, 2012 at 3:16 AM, Shawn Heisey <solr@elyograg.org> wrote:
>
>> On 9/6/2012 6:54 PM, kiran chitturi wrote:
>>
>>> The error i am getting is 'org.apache.solr.common.**SolrException:
>>> Invalid
>>> Date String: '1345743552'.
>>>
>>>   I think it was being saved as a string in DB, so i will use the
>>> DateFormatTransformer.
>>>
>>
>> To go along with all the other replies that you have gotten:  I import
>> from MySQL with a unix format date field.  It's a bigint, not a string, =
but
>> a quick test on MySQL 5.1 shows that the function works with strings too=
.
>>  This is how my SELECT handles that field - I have MySQL convert it befo=
re
>> it gets to Solr:
>>
>> from_unixtime(`d`.`post_date`) AS `pd`
>>
>> When it comes to the character set issues, this is how I have defined th=
e
>> driver in the dataimport config.  The character set in the database is u=
tf8.
>>
>>   <dataSource type=3D"JdbcDataSource"
>>     driver=3D"com.mysql.jdbc.Driver"
>>     encoding=3D"UTF-8"
>> url=3D"jdbc:mysql://${**dataimporter.request.dbHost}:**
>> 3306/${dataimporter.request.**dbSchema}?**zeroDateTimeBehavior=3D**
>> convertToNull"
>>     batchSize=3D"-1"
>>     user=3D"<removed>"
>>     password=3D"<removed>"/>
>>
>> Thanks,
>> Shawn
>>
>>
>

--e0cb4efe35861e001004c955bf7d--