You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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 allexclusion
sections forcitation-matching-core-code
anddocument-similarity-oap-uberworkflow
dependencies defined in IIS. You would get smaller packages.The text was updated successfully, but these errors were encountered: