[
https://issues.apache.org/jira/browse/PARQUET-1992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17293788#comment-17293788
]
Gabor Szadovszky commented on PARQUET-1992:
-------------------------------------------
[~mayaa], the {{integration-test}} you've referenced is a goal of the
{{maven-failsafe-plugin}} not a profile reference. Anyway it is one option to
not to execute these tests (and the related git module update) for the default
profiles. Another way would be to download the required parquet files in a way
that is working if you are not in a git repository (the extracted tarball). One
easy way is to use the direct github links of the actual files (e.g.
https://github.com/apache/parquet-testing/raw/40379b3/data/encrypt_columns_and_footer.parquet.encrypted).
I think, downloading the files has some benefits over updating the whole
github submodule. But I am open to discussions.
> Cannot build from tarball because of git submodules
> ---------------------------------------------------
>
> Key: PARQUET-1992
> URL: https://issues.apache.org/jira/browse/PARQUET-1992
> Project: Parquet
> Issue Type: Bug
> Reporter: Gabor Szadovszky
> Priority: Blocker
>
> Because we use git submodules (to get test parquet files) a simple "mvn clean
> install" fails from the unpacked tarball due to "not a git repository".
> I think we would have 2 options to solve this situation:
> * Include all the required files (even only for testing) in the tarball and
> somehow avoid the git submodule update in case of executed in a non-git
> envrionment
> * Make the downloading of the parquet files and the related tests optional so
> it won't fail the build from the tarball
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
