[jira] [Commented] (ATLAS-1494) Data models of types inheriting Process have Inputs,Outputs which are of very generic type.

["Vimal Sharma (JIRA)" <ji...@apache.org>]

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

Vimal Sharma commented on ATLAS-1494:
-------------------------------------

[~ssainath] I think this is by design. Types inheriting from type Process can connect cross component entities. For example, type "storm_topology" inherits from "Process" and its inputs/outputs can be entities of type "hive_table", "kafka_spout", "hdfs_path".

Imposing constraints on "inputs" and "outputs" of types derived from "Process" sounds reasonable and needs discussion. As you mentioned, we can consider imposing additional constraints on derived types like "falcon_process" to allow specific types in "inputs/outputs".

> Data models of types inheriting Process have Inputs,Outputs which are of very generic type. 
> --------------------------------------------------------------------------------------------
>
>                 Key: ATLAS-1494
>                 URL: https://issues.apache.org/jira/browse/ATLAS-1494
>             Project: Atlas
>          Issue Type: Bug
>          Components:  atlas-core
>            Reporter: Sharmadha Sainath
>
> Types which are inheriting from Process have Inputs,Outputs as attributes of datatype array<DataSet> which is very generic. For example, falcon_process' input and output should be falcon_feed. In case of generic DataSet , input and output can be any DataSet like hive_table, hbase_column_family , jms_topic etc., which is faulty when associated to the falcon_process. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)