keith-turner commented on issue #4684: URL: https://github.com/apache/accumulo/issues/4684#issuecomment-2184169539
> Would it be possible to user an observer and just have Zookeeper send notifications when the node changes for the table name/id? The cache could get updates for table creation and deletions. Discussed this with @cshannon offline. Suspect writing would need custom ZK code to keep the cache up to date. The goal is to have a `Map<TableName, TableId>` however in ZK we have `Map<TableId, TableName>` . With enough custome observers may be able to keep the `Map<TableName, TableId>` up to date based on changes in ZK. An alternative approach may be to create `Map<TableName, TableId>` in zookeeper as an index conceptually. This would make the accumulo client code super simple as it could use zoocache for the `Map<TableName, TableId>` stored in zookeeper. The only problem is this index in ZK needs to be kept consistent. The consistency may not be a problem though because all table operations like create, import, clone, rename, and delete that would need to update this `Map<TableName, TableId>` index in zk already run as fate operations. So the updates to this index could be done via fate. If the code added to fate is simple then a lot of complex client code could be removed and it may result in a net simplification of the code base, not sure though. This would probably not be a change for 2.1.x initially. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
