You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sqoop.apache.org by "Boglarka Egyed (JIRA)" <ji...@apache.org> on 2018/06/04 10:10:00 UTC

[jira] [Comment Edited] (SQOOP-3319) Extract code using Kite into separate classes

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

Boglarka Egyed edited comment on SQOOP-3319 at 6/4/18 10:09 AM:
----------------------------------------------------------------

Latest run was SUCCESSFUL, infra problem seems to be resolved.


was (Author: boglarkaegyed):
Latest run was SUCCESSFUL with a runtime of 16 minutes 40 seconds, infra problem seems to be resolved.

> Extract code using Kite into separate classes
> ---------------------------------------------
>
>                 Key: SQOOP-3319
>                 URL: https://issues.apache.org/jira/browse/SQOOP-3319
>             Project: Sqoop
>          Issue Type: Sub-task
>            Reporter: Szabolcs Vasas
>            Assignee: Szabolcs Vasas
>            Priority: Major
>             Fix For: 3.0.0
>
>         Attachments: SQOOP-3319.patch, SQOOP-3319.patch
>
>
> Kite Dataset API is used in many places in the code to read/write Parquet files and configure MR jobs.
> The goal of this JIRA is to introduce an implementation agnostic interface for Parquet reading/writing and extract the code using Kite Dataset API into separate classes implementing this interface. The benefit of this refactoring is that it enables us introducing a new Parquet reading/writing implementation which does not use Kite but plugs in easily.



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