On Tue, Feb 17, 2015 at 8:21 PM, Aniket Bhoi wrote:
> Hi Folks,
>
> I am running Solr 3.4 and using DIH for importing data from a SQL server
> backend.
>
> The query for Full import and Delta import is the same ie both pull the
> same data.
>
> Full and Del
Hi Folks,
I am running Solr 3.4 and using DIH for importing data from a SQL server
backend.
The query for Full import and Delta import is the same ie both pull the
same data.
Full and Delta import query:
SELECT KB_ENTRY.ADDITIONAL_INFO ,KB_ENTRY.KNOWLEDGE_REF
ID,SU_ENTITY_TYPE.REF ENTRY_TYPE_RE
On Sun, Jul 27, 2014 at 12:28 PM, Gora Mohanty wrote:
> On 27 July 2014 12:13, Aniket Bhoi wrote:
>
> > On Fri, Jul 25, 2014 at 8:32 PM, Aniket Bhoi
> > wrote:
> >
> > > I have Apache Solr,hosted on my apache Tomcat Server with SQLServer
> > > Backend
On Fri, Jul 25, 2014 at 8:32 PM, Aniket Bhoi wrote:
> I have Apache Solr,hosted on my apache Tomcat Server with SQLServer
> Backend.
>
>
> Details:
>
> *Solr Version:*
> Solr Specification Version: 3.4.0.2012.01.23.14.08.01
> Solr Implementation Version: 3.4
> Luc
I have Apache Solr,hosted on my apache Tomcat Server with SQLServer Backend.
Details:
*Solr Version:*
Solr Specification Version: 3.4.0.2012.01.23.14.08.01
Solr Implementation Version: 3.4
Lucene Specification Version: 3.4
Lucene Implementation Version: 3.4
*Tomcat version:*
Apache Tomcat/6.0.1
On Tue, Jun 3, 2014 at 6:28 PM, Shawn Heisey wrote:
> On 6/3/2014 3:04 AM, Aniket Bhoi wrote:
> > I changed the value of removeAbandoned to false,this time the indexing
> > failed due to a different exception:
>
>
>
> > Caused by: com.microsoft.sqlserver.jdbc.
On Sun, Jun 1, 2014 at 10:55 PM, Shawn Heisey wrote:
> On 5/31/2014 1:54 PM, Aniket Bhoi wrote:
> > Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: The result
> >>> set is closed.
>
> I still think this is an indication of the source of the problem.
> S
still awaiting a response from someone
On Tue, May 27, 2014 at 1:35 PM, Aniket Bhoi wrote:
>
>
>
> On Mon, May 26, 2014 at 4:14 PM, Aniket Bhoi
> wrote:
>
>> Another thing I have noted is that the exception always follows a commit
>> operation
On Mon, May 26, 2014 at 4:14 PM, Aniket Bhoi wrote:
> Another thing I have noted is that the exception always follows a commit
> operation.Log excerpt below:
>
> INFO: SolrDeletionPolicy.onCommit: commits:num=2
> commit{dir=/opt/solr/cores/calls/data/index,segFN=segme
Another thing I have noted is that the exception always follows a commit
operation.Log excerpt below:
INFO: SolrDeletionPolicy.onCommit: commits:num=2
commit{dir=/opt/solr/cores/calls/data/index,segFN=segments_2qt,version=1347458723267,generation=3557,filenames=[_3z9.tii,
_3z3.fnm, _3z9.nrm, _3za.
On Thu, May 22, 2014 at 9:31 PM, Shawn Heisey wrote:
> On 5/22/2014 8:31 AM, Aniket Bhoi wrote:
> > On Thu, May 22, 2014 at 7:13 PM, Shawn Heisey wrote:
> >
> >> On 5/22/2014 1:53 AM, Aniket Bhoi wrote:
> >>> Details:
> >>>
> &
On Thu, May 22, 2014 at 7:13 PM, Shawn Heisey wrote:
> On 5/22/2014 1:53 AM, Aniket Bhoi wrote:
> > Details:
> >
> > *Solr Version:*
> > Solr Specification Version: 3.4.0.2012.01.23.14.08.01
> > Solr Implementation Version: 3.4
> > Lucene Specification
..to make sure the thread doesnt time out.
We also killed a lot of sleeping sessions from the server to the database.
All of the above still didnt work
Need help now,I have no clue what is going wrong now.
Regards,
Aniket Bhoi
13 matches
Mail list logo
