You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@metron.apache.org by "Nick Allen (JIRA)" <ji...@apache.org> on 2017/05/05 20:31:04 UTC

[jira] [Commented] (METRON-934) Component and task id are missing in the ndexing topology Hdfs file names

    [ https://issues.apache.org/jira/browse/METRON-934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15998913#comment-15998913 ] 

Nick Allen commented on METRON-934:
-----------------------------------

Is this the same as METRON-674?  https://issues.apache.org/jira/browse/METRON-674

I don't understand the symptoms that you are seeing, so I am not sure.

> Component and task id are missing in the ndexing topology Hdfs file names
> -------------------------------------------------------------------------
>
>                 Key: METRON-934
>                 URL: https://issues.apache.org/jira/browse/METRON-934
>             Project: Metron
>          Issue Type: Bug
>            Reporter: Ryan Merriman
>
> The HdfsWriter class creates a new PathExtensionFileNameFormat object and passes it to SourceHandler class.  However, the PathExtensionFileNameFormat.prepare method is never called, resulting in uninitialized DefaultFileNameFormat.componentId and DefaultFileNameFormat.taskId fields.
> This becomes a problem as soon as a BulkMessageWriterBolt with HdfsWriter configured is given more than one task because the HDFS file name is not unique among tasks (taskId defaults to 0 if not initialized).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)