Dear Shawn,

Thanks for the info. You are right. I have pasted only the client side
stack trace. I failed to check the solr logs. As I went over the logs I
found out that the same fieldnames cannot be created again and again
according to Solr 7.6.0. In Solr 7.2.1, it was not the case. Anyhow I'll
create a separate mail thread to discuss this matter.

Thanks again,

Regards,
Arunan

*Sugunakumar Arunan*
Undergraduate - CSE | UOM

Email : aruna <aru...@wso2.com>ns...@cse.mrt.ac.lk
Mobile : 0094 766016272 <076%20601%206272>
LinkedIn : https://www.linkedin.com/in/arunans23/


On Sun, 20 Jan 2019 at 02:26, Shawn Heisey <apa...@elyograg.org> wrote:

> On 1/19/2019 10:05 AM, Arunan Sugunakumar wrote:
> > I created a project with solrj 7.2.1 which worked perfectly with Apache
> > Solr 7.2. But it does not seem to work with Apache Solr 7.6. I would like
> > to know whether it is mandatory to use the same solrj version as the
> solr.
> >
> > I have pasted the stacktrace for the exception below.
>
> That's not the whole stacktrace.  The whole thing could be hundreds of
> lines long, and if you leave any of it out, understanding it might not
> be possible.  The top of the stacktrace says that the server returned an
> error.  The error from the server will most likely be in the stacktrace
> on the client, but if it's not, you should be able to check the server's
> logs and see it there.
>
> Seeing the SolrJ code that produced the error might become necessary.
>
> HttpSolrClient should be widely compatible across versions.
> CloudSolrClient is where compatibility across a large gap might be
> problematic.  The gap between 7.2 and 7.6 is not large.  If using the
> same version for both isn't possible, best results are obtained when the
> client version is newer than the server version.  Using an older client
> with a newer Solr can be problematic, even when it's not CloudSolrClient.
>
> General client functionality tends to be VERY stable -- queries,
> updates, etc.  I see from the included stacktrace that you're calling
> something you've named "addFieldNameToSchema" ... that is one of Solr's
> specialty capabilities that hasn't been around as long as core
> functionality.  That kind of functionality tends to change more
> frequently than core functionality.
>
> Thanks,
> Shawn
>
>

Reply via email to