You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@chukwa.apache.org by "Aaron Beitch (JIRA)" <ji...@apache.org> on 2009/08/04 03:11:14 UTC
[jira] Created: (CHUKWA-367) Output meta-data with dump.sh.
Output meta-data with dump.sh.
------------------------------
Key: CHUKWA-367
URL: https://issues.apache.org/jira/browse/CHUKWA-367
Project: Hadoop Chukwa
Issue Type: Improvement
Affects Versions: 0.3.0
Reporter: Aaron Beitch
Priority: Minor
Output some meta-data along with file content with dump.sh, such as host and cluster.
Justification: Data can come from many sources; ability to see which node data came from in the output of dump.sh would make things clearer.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CHUKWA-367) Output meta-data with dump.sh.
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CHUKWA-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745653#action_12745653 ]
Hudson commented on CHUKWA-367:
-------------------------------
Integrated in Chukwa-trunk #112 (See [http://hudson.zones.apache.org/hudson/job/Chukwa-trunk/112/])
> Output meta-data with dump.sh.
> ------------------------------
>
> Key: CHUKWA-367
> URL: https://issues.apache.org/jira/browse/CHUKWA-367
> Project: Hadoop Chukwa
> Issue Type: Improvement
> Components: User Interface
> Affects Versions: 0.3.0
> Reporter: Aaron Beitch
> Assignee: Ari Rabkin
> Priority: Minor
> Fix For: 0.3.0
>
> Attachments: CHUKWA-367.patch
>
>
> Output some meta-data along with file content with dump.sh, such as host and cluster.
> Justification: Data can come from many sources; ability to see which node data came from in the output of dump.sh would make things clearer.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CHUKWA-367) Output meta-data with dump.sh.
Posted by "Ari Rabkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CHUKWA-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738762#action_12738762 ]
Ari Rabkin commented on CHUKWA-367:
-----------------------------------
Proposal:
Right now, dump uses a row of dashes to separate streams. Can stick the stream metadata in that separator.
> Output meta-data with dump.sh.
> ------------------------------
>
> Key: CHUKWA-367
> URL: https://issues.apache.org/jira/browse/CHUKWA-367
> Project: Hadoop Chukwa
> Issue Type: Improvement
> Affects Versions: 0.3.0
> Reporter: Aaron Beitch
> Priority: Minor
>
> Output some meta-data along with file content with dump.sh, such as host and cluster.
> Justification: Data can come from many sources; ability to see which node data came from in the output of dump.sh would make things clearer.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CHUKWA-367) Output meta-data with dump.sh.
Posted by "Ari Rabkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CHUKWA-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ari Rabkin updated CHUKWA-367:
------------------------------
Attachment: CHUKWA-367.patch
Note that this conflicts with CHUKWA-366. I'll reconcile, assuming both are approved for committing. Otherwise, I'll regenerate. :)
> Output meta-data with dump.sh.
> ------------------------------
>
> Key: CHUKWA-367
> URL: https://issues.apache.org/jira/browse/CHUKWA-367
> Project: Hadoop Chukwa
> Issue Type: Improvement
> Components: User Interface
> Affects Versions: 0.3.0
> Reporter: Aaron Beitch
> Assignee: Ari Rabkin
> Priority: Minor
> Fix For: 0.3.0
>
> Attachments: CHUKWA-367.patch
>
>
> Output some meta-data along with file content with dump.sh, such as host and cluster.
> Justification: Data can come from many sources; ability to see which node data came from in the output of dump.sh would make things clearer.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CHUKWA-367) Output meta-data with dump.sh.
Posted by "Ari Rabkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CHUKWA-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ari Rabkin updated CHUKWA-367:
------------------------------
Component/s: User Interface
Fix Version/s: 0.3.0
Assignee: Ari Rabkin
> Output meta-data with dump.sh.
> ------------------------------
>
> Key: CHUKWA-367
> URL: https://issues.apache.org/jira/browse/CHUKWA-367
> Project: Hadoop Chukwa
> Issue Type: Improvement
> Components: User Interface
> Affects Versions: 0.3.0
> Reporter: Aaron Beitch
> Assignee: Ari Rabkin
> Priority: Minor
> Fix For: 0.3.0
>
>
> Output some meta-data along with file content with dump.sh, such as host and cluster.
> Justification: Data can come from many sources; ability to see which node data came from in the output of dump.sh would make things clearer.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CHUKWA-367) Output meta-data with dump.sh.
Posted by "Ari Rabkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CHUKWA-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ari Rabkin updated CHUKWA-367:
------------------------------
Status: Patch Available (was: Open)
> Output meta-data with dump.sh.
> ------------------------------
>
> Key: CHUKWA-367
> URL: https://issues.apache.org/jira/browse/CHUKWA-367
> Project: Hadoop Chukwa
> Issue Type: Improvement
> Components: User Interface
> Affects Versions: 0.3.0
> Reporter: Aaron Beitch
> Assignee: Ari Rabkin
> Priority: Minor
> Fix For: 0.3.0
>
> Attachments: CHUKWA-367.patch
>
>
> Output some meta-data along with file content with dump.sh, such as host and cluster.
> Justification: Data can come from many sources; ability to see which node data came from in the output of dump.sh would make things clearer.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CHUKWA-367) Output meta-data with dump.sh.
Posted by "Ari Rabkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CHUKWA-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ari Rabkin updated CHUKWA-367:
------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Taking silence for consent, I just committed this. (Rationale: Change is confined to DumpChunks, which I believe has no users outside Berkeley -- where this change is in production use.)
> Output meta-data with dump.sh.
> ------------------------------
>
> Key: CHUKWA-367
> URL: https://issues.apache.org/jira/browse/CHUKWA-367
> Project: Hadoop Chukwa
> Issue Type: Improvement
> Components: User Interface
> Affects Versions: 0.3.0
> Reporter: Aaron Beitch
> Assignee: Ari Rabkin
> Priority: Minor
> Fix For: 0.3.0
>
> Attachments: CHUKWA-367.patch
>
>
> Output some meta-data along with file content with dump.sh, such as host and cluster.
> Justification: Data can come from many sources; ability to see which node data came from in the output of dump.sh would make things clearer.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.