yanghua commented on pull request #2058:
URL: https://github.com/apache/hudi/pull/2058#issuecomment-691431626
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use
yanghua commented on pull request #2058:
URL: https://github.com/apache/hudi/pull/2058#issuecomment-690838645
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use
yanghua commented on pull request #2058:
URL: https://github.com/apache/hudi/pull/2058#issuecomment-691431626
> Would you mind helping document this if possible ?
OK, my pleasure.
This is an automated message
yanghua commented on pull request #2058:
URL: https://github.com/apache/hudi/pull/2058#issuecomment-690838645
> @yanghua : You can look at the docker compose file and
https://github.com/apache/hudi/blob/master/docker/setup_demo.sh We mount hudi
workspace inside docker to achieve it.
>
yanghua commented on pull request #2058:
URL: https://github.com/apache/hudi/pull/2058#issuecomment-689916526
> If you are referring to hudi, we don't have to rebuild docker images to
pick up latest hudi code.
Yes
> The hudi codebase is mounted inside docker containers so that
yanghua commented on pull request #2058:
URL: https://github.com/apache/hudi/pull/2058#issuecomment-688649831
> @yanghua : Publishing images is done in an adhoc fashion only on demand.
So, IMO, local caching of artifacts is not going to help. W.r.t adaptations, do
you have anything else ot
yanghua commented on pull request #2058:
URL: https://github.com/apache/hudi/pull/2058#issuecomment-688573169
> Are you building docker images somewhere else ?
No, only want to speed up the local build progress. Actually, I do not know
how we publish the official docker image. Do we
yanghua commented on pull request #2058:
URL: https://github.com/apache/hudi/pull/2058#issuecomment-688536635
@bvaradar It seems you are busy?
@leesf Do you have time to verify this PR?
This is an automated message fro
