abstractdog commented on PR #6390: URL: https://github.com/apache/hive/pull/6390#issuecomment-4161644254
> > > > ⠙ hiveserver2-llap Pulling ⠸ hiveserver2 Pulling > > > > is that expected? > > > > > > > > > At what phase you faced that? Please ensure you have > > > ``` > > > export HIVE_VERSION=4.2.0 > > > ./build.sh -hive 4.2.0 -hadoop 3.4.1 -tez 0.10.5 > > > ``` > > > > > > docker compose, are we starting 2 hs2? > > ``` > > 526347bb9f27 apache/hive:4.2.0 "sh -c /entrypoint.sh" 40 seconds ago Up 39 seconds 0.0.0.0:10000->10000/tcp, 9083/tcp, 0.0.0.0:10002->10002/tcp hiveserver2 > > 78b9cddef5cc apache/hive:4.2.0 "sh -c /entrypoint.sh" 40 seconds ago Up 39 seconds 9083/tcp, 10000/tcp, 0.0.0.0:10001->10001/tcp, 10002/tcp, 0.0.0.0:10003->10003/tcp hiveserver2-llap > > ``` > > > > > > > > > > > > > > > > > > > > > > > > i think we should move regular hs2 under tez profile > > Maybe @abstractdog can give proper reply but my understanding is that before llap profile was introduced, a regular hs2 was running, _and after llap profile, a new hiveserver2-llap is introduced_. If we move the regular hs2 under tez profile then we are changing the older behaviour of how the docker command was used by users isn't it? Also, i can't find any tez profile in docker-compose.yml? you mean introduce a new one? exactly, introducing a new profile "tez" or maybe "core"/"local" would solve all the problems of duplicated HS2, but it's also a compatibility problem I was concerned that in case of adding such a profile, the old commands will simply stop working, as according to the current documentation of Docker Compose commands, no profile is used, so keeping using them that way will lead to hs2 not running at all (because user has to explicitly add `--profile ...` after this change) I'm fine saying this is a development tool for now, so we're just updating hive-site repo as well as README, and users will get to know this breaking change sooner or later, is this acceptable for you guys? @deniskuzZ , @Aggarwal-Raghav -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
