[
https://issues.apache.org/jira/browse/BEAM-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16102886#comment-16102886
]
Ismaël Mejía commented on BEAM-2676:
------------------------------------
I don't want to be contentious, but should this really be in core?
As a non-user of the SQL should I care to have this classes? Is this general
enough to use it as our generic Tuple representation to justify this? and in
any case, is this representation mature enough to be in core?
We should at least mark this as Experimental if we proceed, as well as the SQL
module at least until we are really sure we got the APIs right which for sure
won't be in the first release.
> move BeamSqlRow and BeamSqlRowType to sdk/java/core
> ---------------------------------------------------
>
> Key: BEAM-2676
> URL: https://issues.apache.org/jira/browse/BEAM-2676
> Project: Beam
> Issue Type: Test
> Components: dsl-sql
> Reporter: Xu Mingmin
> Assignee: Xu Mingmin
> Labels: dsl_sql_merge
>
> BeamSqlRow/BeamSqlRowType is the fundamental of structured data processing in
> Beam, like joins, simple projections/expansions. It's more visible to move
> them to sdk-java-core.
> It contains two parts:
> 1). remove SQL word in the name,
> BeamSqlRow --> BeamRow
> BeamSqlRowType --> BeamRowType
> 2). move from package {{org.apache.beam.dsls.sql.schema}} to
> {{org.apache.beam.sdk.sd}} (sd stands for structure data), in module
> {{beam-sdks-java-core}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
