[
https://issues.apache.org/jira/browse/BLUR-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13462357#comment-13462357
]
Tim Williams commented on BLUR-22:
----------------------------------
I'm switching it to remove the zk dependency in the BlurTask and instead accept
a controller connection string.
I thought I could piggy back on the TableDescriptor's readonly method but they
don't check the same zookeeper path. The current checkTable logic checks
zookeeper's getLockPath whereas the TableDescriptor.isReadOnly checks
zookeeper's "readonly" path. It actually seems like checking both paths would
be prudent in the isReadOnly check but I'm not sure - can someone shed some
light on this?
> Zookeeper not set in BlurTask job on updates
> --------------------------------------------
>
> Key: BLUR-22
> URL: https://issues.apache.org/jira/browse/BLUR-22
> Project: Apache Blur
> Issue Type: Bug
> Reporter: Tim Williams
>
> When INDEXING_TYPE.UPDATE with a BlurTask, we try to checkTable() on job
> configuration which tries to go to zookeeper, only _zooKeeper is never
> actually set.
> I think it's fair to ask that the "blur.zookeeper.connection" property is set
> on the incoming job Configuration - which would allow ZkUtils.newZooKeeper?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
