You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hudi.apache.org by "vinoyang (Jira)" <ji...@apache.org> on 2019/10/14 12:50:00 UTC

[jira] [Comment Edited] (HUDI-289) Implement a long running test for Hudi writing and querying end-end

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

vinoyang edited comment on HUDI-289 at 10/14/19 12:49 PM:
----------------------------------------------------------

[~vinoth] The first question I want to ask is what do you think about remaining the {{hoodie-bench}} (introduced in the branch of this PR: https://github.com/apache/incubator-hudi/pull/623) or introducing a new module named such as {{hoodie-end-to-end-tests}} like Flink?


was (Author: yanghua):
[~vinoth] The first question I want to ask is what do you think about remaining the {{hoodie-bench}} or introducing a new module named such as {{hoodie-end-to-end-tests}} like Flink?

> Implement a long running test for Hudi writing and querying end-end
> -------------------------------------------------------------------
>
>                 Key: HUDI-289
>                 URL: https://issues.apache.org/jira/browse/HUDI-289
>             Project: Apache Hudi (incubating)
>          Issue Type: Test
>          Components: Usability
>            Reporter: Vinoth Chandar
>            Assignee: vinoyang
>            Priority: Major
>
> We would need an equivalent of an end-end test which runs some workload for few hours atleast, triggers various actions like commit, deltacopmmit, rollback, compaction and ensures correctness of code before every release
> P.S: Learn from all the CSS issues managing compaction.. 



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