[
https://issues.apache.org/jira/browse/ACCUMULO-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13860554#comment-13860554
]
Christopher Tubbs commented on ACCUMULO-1933:
---------------------------------------------
Currently, omitting the "B" implies bytes, as that's the basic unit of memory,
so maybe there's no need to support another way to specify "bytes"? There is
currently no way to specify "bits" (because, as pointed out, that doesn't make
sense). However, I still kinda think allowing "b" is confusing to treat as
"bytes"... especially if you get a pedantic networking person configuring
Accumulo.
Perhaps a good compromise is to allow "K", "M", and "G" to be case-insensitive
(to permit JVM configuration syntax), and leave "B" alone (I'm not sure JVM
even recognizes "B")? We could continue to document the upper-case as a
preference, but be more tolerant of lower-case, for these. That would satisfy
the vast majority of cases, anyway, since the whole reason for being able to
specify units is to make it easier to specify kilobytes, megabytes, and
gigabytes... not bytes.
> Make unit on memory parameters case-insensitive
> -----------------------------------------------
>
> Key: ACCUMULO-1933
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1933
> Project: Accumulo
> Issue Type: Improvement
> Components: shell
> Affects Versions: 1.5.0
> Reporter: Josh Elser
> Priority: Minor
> Labels: newbie
>
> {{config -t my_table -s table.split.threshold=2g}} fails with a non-intuitive
> error.
> {{config -t my_table -s table.split.threshold=2G}} succeeds
> It would be nice for both to work.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
