[
https://issues.apache.org/jira/browse/CHUKWA-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12739088#action_12739088
]
Ari Rabkin commented on CHUKWA-366:
-----------------------------------
Yes. My patch is leveraging chukwaAgent.tags, and addTag(). It makes no
change to that part of the system. As you point out, it is implicitly
standardizing key="value"; or at least encouraging that format. You'd still be
able to use that field in other ways, but callers of getTag(String ) would be
confused. I'm prepared to pay that price.
Rather than adding a Map to Chunk, you might extend ChunkImpl to include your
map, if you don't need to serialize it. This would preserve the existing
serialized format.
> Custom Tags
> -----------
>
> Key: CHUKWA-366
> URL: https://issues.apache.org/jira/browse/CHUKWA-366
> Project: Hadoop Chukwa
> Issue Type: New Feature
> Components: User Interface
> Affects Versions: 0.3.0
> Environment: Web Stack
> Reporter: Aaron Beitch
> Assignee: Ari Rabkin
> Fix For: 0.3.0
>
> Attachments: generaltagging.patch
>
>
> Being able to specify custom tags for a machine.
> I would like to be able to tag a machine as part of a specific stack, such as
> Stack1 and Stack2, which is already implemented as the 'cluster' tag
> specified in chukwa-agent-conf.xml. I would also like to be able to tag each
> machine according to its role, such as WebServer or DataBase. This is not
> currently doable. The best solution would probably be to allow arbitrary
> tags. This functionality should be exposed also in the use of dump.sh, such
> that I can filter on any tag.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
