[jira] [Comment Edited] (BEAM-3647) Default Coder/Reading Coder From File

2018-02-14 Thread Kishan Kumar (JIRA)

[ 
https://issues.apache.org/jira/browse/BEAM-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16365147#comment-16365147
 ] 

Kishan Kumar edited comment on BEAM-3647 at 2/15/18 4:55 AM:
-

Thanks [~jkff] I need to Specify That 

PCollection inputTable = PBegin.in(p).apply(Create.of(row1, row2, row3)
.*withCoder(type.getRowCoder()*));

 

The Coder Can We Choose at Run Time Because the Same Query is Going to Run on 
Different DDL as Shown Above in Example Because Seeing the Above *Case* I have 
not Found Such Use Case.

 

And the Same Question I have Asked at StackOverflow -: 
https://stackoverflow.com/questions/47806368/running-beamsql-withoutcoder-or-making-coder-dynamic


was (Author: kishank):
[~jkff] I need to Specify That 

PCollection inputTable = PBegin.in(p).apply(Create.of(row1, row2, row3)
.*withCoder(type.getRowCoder()*));

 

The Coder Can We Choose at Run Time Because the Same Query is Going to Run on 
Different DDL as Shown Above in Example Because Seeing the Above *Case* I have 
not Found Such Use Case.

> Default Coder/Reading Coder From File 
> --
>
> Key: BEAM-3647
> URL: https://issues.apache.org/jira/browse/BEAM-3647
> Project: Beam
>  Issue Type: New Feature
>  Components: beam-model, dsl-sql
>Affects Versions: 2.2.0
>Reporter: Kishan Kumar
>Priority: Major
> Fix For: 2.1.0
>
>
> *Requirement*-: Need to Run Template With Same Logics on Different Tables 
> Data.(Example is Given Below)
>  
> *Need*: Default Coder is Required So According to Data It Make All Fields as 
> String and Read Data else Thier must be Dynamic Options to Read Coder From 
> GCS as JSON FILE and Parse Data on Basis of That (But We can Pass Location 
> Using ValueProvider) or SomeWhere Else so At Runtime Using ValueProvider.
>  
>  
> *Examples*: I Have Two Tables 1 is Having Column (NAME, CLASS, ROLL, 
> SUB_PRICE)
> And 2 Table is (NAME, ROLL, SUB, TEST_MARKS)
>  
> On Both Tables, I am Just Sorting Table on Basis Of Roll Number so if We can 
> Read Coder at Run Time The Same Template Can Be Used For Different Tables at 
> Run Time.
>  
> Such Situations Make Our Work Easy and Make Our job Easy.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Comment Edited] (BEAM-3647) Default Coder/Reading Coder From File

2018-02-12 Thread Kishan Kumar (JIRA)

[ 
https://issues.apache.org/jira/browse/BEAM-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16361880#comment-16361880
 ] 

Kishan Kumar edited comment on BEAM-3647 at 2/13/18 6:37 AM:
-

Thanks,[~kenn] and [~kedin]   But I want to State That For Different Use Case 
We are Using Two Different Templates Because We need to Define Codertheirr Only 
If We can Read Coder at Run Time Then Both Work can Be Done in Single Template 
Because On Both The SQl Selection is Done on Roll Number Only.


was (Author: kishank):
Thanks,[~kenn] and [~kedin]

> Default Coder/Reading Coder From File 
> --
>
> Key: BEAM-3647
> URL: https://issues.apache.org/jira/browse/BEAM-3647
> Project: Beam
>  Issue Type: New Feature
>  Components: beam-model, dsl-sql
>Affects Versions: 2.2.0
>Reporter: Kishan Kumar
>Priority: Major
>
> *Requirement*-: Need to Run Template With Same Logics on Different Tables 
> Data.(Example is Given Below)
>  
> *Need*: Default Coder is Required So According to Data It Make All Fields as 
> String and Read Data else Thier must be Dynamic Options to Read Coder From 
> GCS as JSON FILE and Parse Data on Basis of That (But We can Pass Location 
> Using ValueProvider) or SomeWhere Else so At Runtime Using ValueProvider.
>  
>  
> *Examples*: I Have Two Tables 1 is Having Column (NAME, CLASS, ROLL, 
> SUB_PRICE)
> And 2 Table is (NAME, ROLL, SUB, TEST_MARKS)
>  
> On Both Tables, I am Just Sorting Table on Basis Of Roll Number so if We can 
> Read Coder at Run Time The Same Template Can Be Used For Different Tables at 
> Run Time.
>  
> Such Situations Make Our Work Easy and Make Our job Easy.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)