[ 
https://issues.apache.org/jira/browse/SAMZA-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Xinyu Liu updated SAMZA-1245:
-----------------------------
    Description: 
For certain system such as hdfs, the physical stream name might need to be 
finalized during the config generation. For example, we might allow user to 
specify the physical name to be the following path:

hdfs:/some/path/data/latest

and it will be translated to an actual path like (hdfs://some/path/data/00) 
when the application starts and generates the config for execution. So in order 
to do that, we will need to expose the stream physical name string for setting 
it in the config.

  was:
For certain system such as hdfs, the physical stream name might need to be 
finalized during the config generation. For example, we might allow user to 
specify the physical name to be the following path:

hdfs:/some/path/data/latest

and it will be translated to an actual path when the application starts and 
generates the config for execution. So in order to do that, we will need to 
expose the stream physical name string for setting it in the config.


> Expose stream physical name config name
> ---------------------------------------
>
>                 Key: SAMZA-1245
>                 URL: https://issues.apache.org/jira/browse/SAMZA-1245
>             Project: Samza
>          Issue Type: Improvement
>            Reporter: Xinyu Liu
>            Assignee: Xinyu Liu
>
> For certain system such as hdfs, the physical stream name might need to be 
> finalized during the config generation. For example, we might allow user to 
> specify the physical name to be the following path:
> hdfs:/some/path/data/latest
> and it will be translated to an actual path like (hdfs://some/path/data/00) 
> when the application starts and generates the config for execution. So in 
> order to do that, we will need to expose the stream physical name string for 
> setting it in the config.



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

Reply via email to