-
Notifications
You must be signed in to change notification settings - Fork 591
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
Package a RisingWave image that supports HDFS after each release #12723
Comments
This issue has been open for 60 days with no activity. Could you please update the status? Feel free to continue discussion or close as not planned. |
seems like the guidance to package is a internal doc, looking forward this feature or any suggestion to mannual package with 1.5.x? |
Hi @sheltonsuen , indeed it's an internal doc, and we can provide a 1.5.x image that supports HDFS if you need. Could you please let us know your hdfs version? |
thanks, It's fine, after using the 1.2 image, working as expected |
You mean you are using RisingWave 1.2 on HDFS, and everything works well? |
sorry about the confusing, I mean this image: RW_v1.2_HDFS_v2.7-x86_64 |
I see. We will deliver a new version later, and will let you know here~ |
This issue has been open for 60 days with no activity. Could you please update the status? Feel free to continue discussion or close as not planned. |
Currently we support HDFS as storage backend but it's off by default, thus we should package a RisingWave image that supports HDFS after each release. We need to package manually on EC2 instead of using buildkite, I have write a guidance to explain how to package it.
https://www.notion.so/risingwave-labs/Package-RisingWave-with-HDFS-6ea9e37568bd4e1882b9217efdc5981b?pvs=4
Note that
libhdfs
is always upwardly compatible, so we only need to package a lower version of HDFS. Let us use HDFS 2.7.3 as the default (the same with Databend).I have package one for v1.2 here, and we need need to do this every time we release from now on.
The text was updated successfully, but these errors were encountered: