Hi, Thank you for your response.
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. When i index a text field which has arabic and English like this tweet “@anaga3an: هو سعد الحريري بيعمل ايه غير تحديد الدوجلاس ويختار الكرافته ؟؟” #gcc #ksa #lebanon #syria #kuwait #egypt #سوريا with field_type as 'text_ar' and when i try to see the same field again in solr, it is shown as below. RT @AhmedWagih: لو معملناش Øاجة Ù�ÙŠ الزيادة السكانية Ù�ÙŠ مصر، هنتØول لدولة Ù�قيرة كثيÙ�Ø© السكان زي بنجلادش #Egypt #EgyEconomy both of the lines do not mean the same, but i have just placed them here as an example. This was the problem i am facing. Many Thanks, Kiran On Thu, Sep 6, 2012 at 8:29 PM, Chris Hostetter <hossman_luc...@fucit.org>wrote: > > : I am using Solr with DIH and started getting errors when the database > : time/date fields are getting imported in to Solr. I have used the date as > > what actual error are you getting? > > If you are pulling dates from a SQL Date field, that the jdbc driver > returns as java.util.Date objects, then you shouldn't need to do anything > special, they should import just fine with solr's TrieDateField. > > if you are importing from something where you really need to convert > yourself (ie: XML files, or string columns in a DB), there is the DIH > DateFormatTransformer... > > https://wiki.apache.org/solr/DataImportHandler#DateFormatTransformer > > : Also, When i used field_type as 'text_ar' and indexed a line with arabic > : text, Solr is displaying some non-ISO characters. It looks like the text > is > : not being unicoded. > > "unicode" is not a verb, so i'm not sure what you mean by "displaying some > non-ISO characters" and "text is not being unicoded" .. please provide a > specific example of hte problem you are facing, including details on what > the source data is. > > > -Hoss > -- Kiran Chitturi
