Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider using provided scope for hadoop dependencies #420

Open
marekhorst opened this issue Jan 18, 2017 · 1 comment
Open

Consider using provided scope for hadoop dependencies #420

marekhorst opened this issue Jan 18, 2017 · 1 comment

Comments

@marekhorst
Copy link
Member

I am working on IIS dependencies cleanup and I realised we have one special exclusion case (among 2-3 others): excluding hadoop libraries from CoAnSys dependencies used in IIS to prevent them from appearing in packages uploaded to cluster.

Since most of the hadoop dependencies are already available on CDH5 cluster we don't need to provide them explicitly in uploaded package. This is how we operate in IIS what allow us making oozie packages significantly smaller.

Have you considered using provided scope for CDH5 hadoop dependencies? This would allow us dropping all exclusion sections for citation-matching-core-code and document-similarity-oap-uberworkflow dependencies defined in IIS. You would get smaller packages.

@acz-icm
Copy link
Collaborator

acz-icm commented Jan 24, 2017

We intend to simplify dependencies in the CoAnSys project. This will allow to set some dependencies as "provided". For the moment, it is not possible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants