You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@eagle.apache.org by "Edward Zhang (JIRA)" <ji...@apache.org> on 2016/02/13 18:44:18 UTC
[jira] [Updated] (EAGLE-155) java API to create metadata before run
end-2-end unit test
[ https://issues.apache.org/jira/browse/EAGLE-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Edward Zhang updated EAGLE-155:
-------------------------------
Description:
Some unit test needs end-2-end run of storm topology. End-2-end testing usually requires import metadata by curl script, but it is not convenient for writing end-2-end unit test.
To encourage people to write end-2-end unit test, we can develop java API to import metadata. This will use the JIRA EAGLE-153 to remotely create table and metadata
was:
Some unit test needs end-2-end run of storm topology. End-2-end testing usually requires import metadata by curl script, but it is not convenient for writing end-2-end unit test.
To encourage people to write end-2-end unit test, we can develop java API to import metadata. This will use the JIRA EAGLE-15
> java API to create metadata before run end-2-end unit test
> ----------------------------------------------------------
>
> Key: EAGLE-155
> URL: https://issues.apache.org/jira/browse/EAGLE-155
> Project: Eagle
> Issue Type: Improvement
> Reporter: Edward Zhang
>
> Some unit test needs end-2-end run of storm topology. End-2-end testing usually requires import metadata by curl script, but it is not convenient for writing end-2-end unit test.
> To encourage people to write end-2-end unit test, we can develop java API to import metadata. This will use the JIRA EAGLE-153 to remotely create table and metadata
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)