[
https://issues.apache.org/jira/browse/PARQUET-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15123632#comment-15123632
]
Wes McKinney commented on PARQUET-479:
--------------------------------------
I definitely don't want to bloat the git repo. So if we go that route, either
we would host test data files outside of the main git repo or have a data
generation script that creates them from scratch locally. parquet-mr probably
never had to face this issue because it was the proverbial chicken.
My preference would be to focus on testing round-tripping data from the ground
up, but I also need to be able to write Parquet files =) It might be useful to
have some "smoke tests" that use external pre-generated data files but it
doesn't feel like a scalable solution (e.g. bug fixes may require generating
the right file to reproduce a bug).
> Improve/expand functional unit tests
> ------------------------------------
>
> Key: PARQUET-479
> URL: https://issues.apache.org/jira/browse/PARQUET-479
> Project: Parquet
> Issue Type: Improvement
> Components: parquet-cpp
> Affects Versions: cpp-0.1
> Reporter: Aliaksei Sandryhaila
> Assignee: Aliaksei Sandryhaila
> Fix For: cpp-0.1
>
>
> We need to add a testing framework for unit tests, and run it as a part of
> each Travis CI build.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
