accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-3122) Rename per-table custom tag property prefix
Date Sun, 14 Sep 2014 20:37:33 GMT


Christopher Tubbs commented on ACCUMULO-3122:

The idea isn't to change the API, just the property prefix. Yes, they're still properties,
and that wouldn't change.

Distinguishing them as user-controlled is the primary intent of the name. "custom" sort of
does that, but I thought "tag" might be familiar to many users, due to things like ID3 tags,
EXIF tags, EC2 tags, etc. Maybe "label" might also work. We could always be quite explicit:
{{table.userDefinedLabel.\*}}, but that lacks elegance.

> Rename per-table custom tag property prefix
> -------------------------------------------
>                 Key: ACCUMULO-3122
>                 URL:
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: client
>            Reporter: Christopher Tubbs
>            Priority: Trivial
>              Labels: api, docuentation, naming
>             Fix For: 1.7.0
> I'm not 100% sold on the name of the {{table.custom.\*}} prefix added in ACCUMULO-2841.
I think a better name might be {{table.tag.\*}} or similar, and I'm leaning towards that.
*Tag* might be better vocabulary to use, especially when discussing the feature in the documentation,
and the property prefix name should be consistent with how we refer to the feature.
> I'm creating this issue to provide a forum for property name suggestions/informal votes/comments,
so the name can be solidified before the feature manifests in a release. I don't want to change
it to *tag* now, and then tomorrow change it again in favor of a better name.

This message was sent by Atlassian JIRA

View raw message