When the user sets a per table prop, they ask the master to do it
(because it can write to zookeeper, user can not). If the users
credentials check out and they have alter table permission, then makes
the change in zookeeper.
Most of the server code just needs to read the properties and has no
need to modfy it. Consequently the code used to read these props by
server code has no set method because its not needed.
On Fri, Jan 4, 2013 at 7:40 AM, David Medinets <[EMAIL PROTECTED]> wrote:
> I did try to use that method. The Property.LOAD_BALANCER that I used
> was not changed when the LoadTableBalancer class retrieved it from the
> TableConfigurations. Then I looked at the source code in
> TableOperationsImpl. setTableProperty does something through the
> Thrift interface. Would that work for unit testing? Either way, I
> don't see how the Thift calls eventually set the property into a
> TableConfiguration object.
> I can add some plumbing needed for dependency injection. Doing so
> seems fairly harmless.
> On Thu, Jan 3, 2013 at 10:10 PM, John Vines <[EMAIL PROTECTED]> wrote:
>> Are you looking for connector.TableOperations().setTableProperty?
>> On Thu, Jan 3, 2013 at 10:09 PM, David Medinets <[EMAIL PROTECTED]>wrote:
>>> I am looking for a way to set the table configuration. I see 122
>>> references to getTableConfiguration but 0 to setTableConfiguration.
>>> There is one usage of "new TableConfiguration" which seems to create
>>> an empty configuration. Have I missed something?