[
https://issues.apache.org/jira/browse/SOLR-2899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150491#comment-13150491
]
Jens Zastrow commented on SOLR-2899:
------------------------------------
As a workaround we defined an NOP SqlEntityProcessor.
package org.apache.solr.handler.dataimport;
public class ContextPropagationSQLEntityProcessor extends SqlEntityProcessor {
@Override
public void init(Context context) {
super.init(context);
if (Context.CURRENT_CONTEXT.get() == null) {
Context.CURRENT_CONTEXT.set(context);
}
}
}
> Custom DIH Functions in Delta-Query have null Context
> -----------------------------------------------------
>
> Key: SOLR-2899
> URL: https://issues.apache.org/jira/browse/SOLR-2899
> Project: Solr
> Issue Type: Bug
> Affects Versions: 3.4
> Reporter: Jens Zastrow
> Priority: Blocker
> Labels: custom, dih, functions
>
> We must use a custom fucntion in the deltaQuery, but the passed in Context is
> always null, preventing any variable resolution.
> In full-import mode behavior is correct.
> Looking into the sources showed that the Conext is used from a thread-local
> Context.CURRENT_CONTEXT.get(),
> wich is never set by (Context.CURRENT_CONTEXT.set()) for the Context created
> in DocBuilder.java:871
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
