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

[GLUTEN-5982][VL] Allow replacing installed minio package in 1.1.1 branch #5983

Closed

Conversation

deepashreeraghu
Copy link
Contributor

What changes were proposed in this pull request?

Allowing replace of minio package for branch 1.1.1

Fixes: #5982

How was this patch tested?

I ran a build with this fix and now it proceeds further and does not fail at rpm -i minio step.

Copy link

github-actions bot commented Jun 4, 2024

Thanks for opening a pull request!

Could you open an issue for this pull request on Github Issues?

https://github.com/oap-project/gluten/issues

Then could you also rename commit message and pull request title in the following format?

[GLUTEN-${ISSUES_ID}][COMPONENT]feat/fix: ${detailed message}

See also:

@PHILO-HE PHILO-HE changed the title Issue 5982 : Allow replacing installed minio package in 1.1.1 branch [GLUTEN-5982][VL] Allow replacing installed minio package in 1.1.1 branch Jun 5, 2024
Copy link

github-actions bot commented Jun 5, 2024

#5982

@PHILO-HE
Copy link
Contributor

PHILO-HE commented Jun 5, 2024

@deepashreeraghu, could you change the target to main branch? There will be no more release in 1.1 branch.

@FelixYBW
Copy link
Contributor

FelixYBW commented Jun 5, 2024

It's an environment issue. It's actually not only minio, but all the dependency libraries which causes version conflict.

So we shouldn't put it in get_velox.sh. Current recommendation is to build Gluten on a clean OS or docker. Otherwise there will be plenty of issues. So let's put the solution in issue.

@PHILO-HE

@PHILO-HE
Copy link
Contributor

PHILO-HE commented Jun 5, 2024

It's an environment issue. It's actually not only minio, but all the dependency libraries which causes version conflict.

So we shouldn't put it in get_velox.sh. Current recommendation is to build Gluten on a clean OS or docker. Otherwise there will be plenty of issues. So let's put the solution in issue.

@PHILO-HE

@FelixYBW, yes, all other libs installed similarly should also have this potential issue.

@FelixYBW
Copy link
Contributor

FelixYBW commented Jun 5, 2024

@FelixYBW, yes, all other libs installed similarly should also have this potential issue.

@deepashreeraghu can you put the error message and the solution in the issue? Looks it's not a good idea to solve the conflict in get_velox.sh. We should keep the script as simple as possible because we need to maintain it during daily velox rebase.

@deepashreeraghu
Copy link
Contributor Author

deepashreeraghu commented Jun 5, 2024

@FelixYBW and @PHILO-HE - Thanks for your response.
I did start with a clean image to build. But while building I hit into some failures and then I retried the build locally ( to find what was the build issue actually) That retry fails even before it reaches the actual failure because it has minio on it already.
I did not face the same trouble with other packages. Hence requested this Pull request so that builds can go through fine when being retried.

@deepashreeraghu
Copy link
Contributor Author

Also, I am building on 1.1.1 because I wanted S3 support which is not available in the released jar.
But, this branch does have a lot of other goodness in it and hence I opted for this branch and trying a dev build.

@deepashreeraghu
Copy link
Contributor Author

In the main branch the same fix is already present.

@FelixYBW
Copy link
Contributor

FelixYBW commented Jun 5, 2024

I see.
Looks you already submitted a PR to Velox: facebookincubator/velox#10044
It's the right place to fix.

@deepashreeraghu
Copy link
Contributor Author

Since the fix will get into Velox as part of the PR - facebookincubator/velox#10044.
Closing this PR.

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

Successfully merging this pull request may close these issues.

None yet

4 participants