[ 
https://issues.apache.org/jira/browse/BEAM-6820?focusedWorklogId=214880&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-214880
 ]

ASF GitHub Bot logged work on BEAM-6820:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 18/Mar/19 16:57
            Start Date: 18/Mar/19 16:57
    Worklog Time Spent: 10m 
      Work Description: goldfishy commented on issue #8069: [BEAM-6820] 
Cassandra object mapper abstraction
URL: https://github.com/apache/beam/pull/8069#issuecomment-474005677
 
 
   Awesome, that would be great. I had to clean up some pre-commit issues.  
Tell me if you want me to open a cleaner PR. 
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 214880)
    Time Spent: 1h 10m  (was: 1h)

> Custom Row-Object mapper implementation for CassandraIO
> -------------------------------------------------------
>
>                 Key: BEAM-6820
>                 URL: https://issues.apache.org/jira/browse/BEAM-6820
>             Project: Beam
>          Issue Type: Improvement
>          Components: io-java-cassandra
>            Reporter: Max Charas
>            Assignee: Max Charas
>            Priority: Minor
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> The current Cassandra source sink is tightly coupled to the Datastax Object 
> Mapper. [This requires 
> users|https://docs.datastax.com/en/developer/java-driver/3.1/manual/object_mapper/]
>  of the sink to provide a POJO describing  the table in Cassandra. Although 
> the POJO is a easy and powerful way to describe the table it does requires 
> users to always recompile the pipeline for each change in the table 
> definition. 
> I suggest adding a abstraction layer that allows users to inject their own 
> mapper implementation. One example use would be a mapper that works with a 
> generic 
> [Row|https://beam.apache.org/releases/javadoc/2.4.0/org/apache/beam/sdk/values/Row.html]
>  implementation rather than a compile-time POJO. 
> This abstraction layer could be implemented by simply supplying a 
> MapperFactory through the Sink/Source builder. 



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

Reply via email to