You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Neal Sidhwaney (JIRA)" <ji...@apache.org> on 2019/07/19 09:49:00 UTC
[jira] [Updated] (SOLR-13643) ResponseBuilder should provide
accessors/setters for analytics response handling
[ https://issues.apache.org/jira/browse/SOLR-13643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Neal Sidhwaney updated SOLR-13643:
----------------------------------
Status: Patch Available (was: Open)
> ResponseBuilder should provide accessors/setters for analytics response handling
> --------------------------------------------------------------------------------
>
> Key: SOLR-13643
> URL: https://issues.apache.org/jira/browse/SOLR-13643
> Project: Solr
> Issue Type: Task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Response Writers
> Affects Versions: 8.1.1
> Reporter: Neal Sidhwaney
> Priority: Trivial
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Right now inside o.a.s.h.c.AnalyticsComponent.java, fields inside ResponseBuilder are accessed directly. Since they're in the same package, this is OK at compile tie. But when the Solr core and Analytics jars are loaded at runtime by Solr, they are done by different classloaders, which causes an IllegalAccessError during request handling. There must be soething different about y setup which is why I am running into this, but it seems like a good idea to abstract away the fields behinds setters/getters anyway.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org