[
https://issues.apache.org/jira/browse/ACCUMULO-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14074948#comment-14074948
]
David Medinets edited comment on ACCUMULO-3022 at 7/25/14 9:26 PM:
-------------------------------------------------------------------
How many, let's say, 200 character table names does it take to exhaust the
Zookeeper memory and why would that be an Accumulo issue? Plucking a number out
of the air, we could say that 2,500 table names of 200 characters each exhaust
Zookeeper memory. If we arbitrarily limit table names to 100 characters then
Zookeeper memory would be exhausted after 5,000 tables were created? It seems
like table name size should be a guideline not an enforceable constraint. You
have to know that six months after the constraint is added, someone will have a
use case for longer table names and then we'll need to make the constraint
configurable.
Oh.. and does this need to have 'Major' priority?
was (Author: medined):
How many, let's say, 200 character table names does it take to exhaust the
Zookeeper memory and why would that be an Accumulo issue? Plucking a number out
of the air, we could say that 2,500 table names of 200 characters each exhaust
Zookeeper memory. If we arbitrarily limit table names to 100 characters then
Zookeeper memory would be exhausted after 5,000 tables were created? It seems
like table name size should be a guideline not an enforceable constraint. You
have to know that six months after the constraint is added, someone will have a
use case for longer table names and then we'll need to make the constraint
configurable.
> Limit size of table names
> -------------------------
>
> Key: ACCUMULO-3022
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3022
> Project: Accumulo
> Issue Type: Improvement
> Affects Versions: 1.4.0
> Reporter: Keith Turner
> Fix For: 1.7.0
>
>
> This issue is inspired by ACCUMULO-3021.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
