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

Rion Williams edited comment on BEAM-10027 at 5/20/20, 4:07 PM:
----------------------------------------------------------------

Any feedback on this issue would be welcome with regards to implementation or a 
preferred method for going about implementing it. I've worked with Kotlin as a 
primary language when using Beam and have previously converted [the existing 
Stepik Beam Katas - Java course|[https://stepik.org/course/54530]] internally 
for myself and my team to work through, so it'd be great to share with the 
community.


was (Author: rionmonster):
Any feedback on this issue would be welcome with regards to implementation or a 
preferred method for going about implementing it. I've worked with Kotlin as a 
primary language when using Beam and have previously converted [the existing 
Stepik Beam Katas - Java course]([https://stepik.org/course/54530]) internally 
for myself and my team to work through, so it'd be great to share with the 
community.

> Support for Kotlin-based Beam Katas
> -----------------------------------
>
>                 Key: BEAM-10027
>                 URL: https://issues.apache.org/jira/browse/BEAM-10027
>             Project: Beam
>          Issue Type: Improvement
>          Components: katas
>            Reporter: Rion Williams
>            Assignee: Rion Williams
>            Priority: P2
>   Original Estimate: 8h
>          Time Spent: 10m
>  Remaining Estimate: 7h 50m
>
> Currently, there are a series of examples available demonstrating the use of 
> Apache Beam with Kotlin. It would be nice to have support for the same Beam 
> Katas that exist for Python, Go, and Java to also support Kotlin. 
> The port itself shouldn't be that involved since it can still target the JVM, 
> so it would likely just require the inclusion for Kotlin dependencies and a 
> conversion for all of the existing Java examples. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to