[
https://issues.apache.org/jira/browse/ACCUMULO-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14180913#comment-14180913
]
Josh Elser commented on ACCUMULO-3176:
--------------------------------------
bq. Unless we disallow non-creation-time table properties, creation time
properties still aren't a real solution.
Do you mean that the update of a table property at some point in time (after it
exists) is subject to the same race condition? That's definitely true. I'd
speculate that the issue is possibly less heinous for
iterators/combiners/constraints because it's likely that you only set at table
creation but that's subjective.
bq. we force a refresh of properties related to a table when it transitions
from offline to online?
It's not clear to me how this would work either. You could probably invalidate
the table properties when a tablet is loaded on a tserver, which would
encompass the offline->online transition. I think that could work. I don't like
the story of "just offline and re-online your table to make sure configuration
propagates". That's really nasty.
Are we at least in agreement that allowing properties at table creation do
mitigate the potential race condition? We would definitely need something more
heavy-handed to properly fix this (or we'd have to do away with ZooCache...)
that is probably out of scope for this issue specifically.
> Add ability to create a table with user specified initial properties
> --------------------------------------------------------------------
>
> Key: ACCUMULO-3176
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3176
> Project: Accumulo
> Issue Type: Sub-task
> Reporter: Jenna Huston
> Assignee: Jenna Huston
>
> This change would allow for table properties to be set before the default
> tablet is created. Instead of just adding a new create method, a
> NewTableConfiguration class could be created and passed and the other create
> methods deprecated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
