jfsii commented on PR #4620: URL: https://github.com/apache/hive/pull/4620#issuecomment-1701741745
Re: @ayushtkn I think my response earlier may have been too strong (maybe I woke up grumpy). Your points are valid and fair, as are mine. They should be considered which is why I would like a 3rd opinion. > Research about other systems. We had also done this research. The point in prior comments is that other systems do not output multiple lines. > Maybe I am checking the wrong pages or did something wrong while trying these commands. No, you are not wrong here. > This is actually documented in the Hadoop Compat guidelines, which Hive was a part Thank you for sharing this document. I would consider Hive and Hadoop/Hdfs different projects with different guidelines, policies and goals. (However, I am not a committer here and I may not be familiar with how these policies are applied to Hive). I agree with what I think the intent of this guideline is - which is to not break consumers of the CLI in which automation is built around or other consumers use. I'd argue that this shouldn't be a "must" for Hive SQL statement output (maybe for beeline output and options) - but we ALSO should take care not to change things that complicate the lives of the users of Hive. > The answer is Never, we aren't allowed to break compatibility, we break it only incase of unavoidable circumstances following a certain pattern, like deprecating and stuff like that, that also can be surpassed in case of security issues and things like that. This is what my limited experience in the ecosystem says. I think this is an unreasonable viewpoint. I think there should be point in time in which backwards compatibility should be able to broken in order to move the project forward and/or to remove features that no longer make sense. However - on the other hand I think there are areas where Hive should get better at this and it is important to call them out for discussion (like you are doing here). Again, we can find consensus here and move forward. I prefer consistency all ;'s or no ;'s - but I can also live with your suggestion of single line having none and multi-statement having ;'s. -- 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]
