accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Josh Elser <>
Subject Re: TabletLocator API stability / alternates?
Date Thu, 06 Nov 2014 00:31:57 GMT
I don't think there is any class/method that we consider to be in our 
"Public API" that does what you want.

You're also not the first one that has tried to do something using 
TabletLocator and has been bitten by it 

At this point, I think we should look at bringing tablet locality into 
the public API for 1.7.0 or 2.0.0. Would you be interested in filing an 
issue on JIRA and helping to flesh out the functionality requirements?

Chris Bennight wrote:
> So we have some code (a custom input format for data persisted in accumulo
> with a custom indexing scheme (geospatial/n-dimensional)):
> The intent behind this was to provide better locality and split information
> since we have a bit more application specific knowledge available than the
> general use case.
> I'm pretty sure there's no other way to get this locality information other
> than using the TableLocator class.
> The arguments + ordering change for TCredentials to Credentials and the
> method signature from getInstance() to getLocator() are the two things
> breaking our 1.5.1 ->  1.6.x compatibility.
> (specifically:
> )
> It's pretty obvious from the diff these were intentional - so no joy there
> in accidental changes that could be fixed.
> Are we just to far down in the weeds, and are going to have to deal with
> supporting multiple versions/breaking changes (via refactoring, dropping
> support, or maven-munge maybe), or is this class/methods/signatures
> expected to be pretty stable now?
> (Or is there a better/more supported way of getting tablet locality
> information?)

View raw message