amanraj2520 commented on PR #3973: URL: https://github.com/apache/hive/pull/3973#issuecomment-1416722510
@zabetak What I meant is that when this change was committed to OSS master, then there was no specific JIRA created for this issue back then. It was done only under HIVE-20593 addendum patch. In order to fix this issue I compared the load_data_using_job.q.out between OSS/master and current branch-3(without this commit). The diff in these lines lead me to this commit https://github.com/apache/hive/commit/dca6ef04e376ea1e18cd8986c3baf210b51d7677 which was done in OSS/master without any JIRA ticket being created for this commit. If you go to this commit it simply says HIVE-20593 addendum patch. Not sure why there was no specific JIRA created for this test failure.  In order to answer your question why these tests did not fail on branch-3 even if HIVE-20593 has been on branch-3 for a long time is as follows: http://ci.hive.apache.org/blue/organizations/jenkins/hive-precommit/detail/PR-3847/1/tests - There was no Jenkins file committed to branch-3 before. Thats why I decided that when we do the 3.2.0 release from branch-3, I would ensure that all the test pass in branch-3. This is the first commit that I had made after committing the Jenkins file to branch-3(which means that this was the first pull request which ran the jenkins pipeline for the tests). I see the test failure even here : (Link : http://ci.hive.apache.org/blue/organizations/jenkins/hive-precommit/detail/PR-3847/1/tests) Attached the snapshot as well.  Can you please ping a link where you find this test passing because I think that as far as all the PR's I have merged in branch-3, I find this test failing in every PR since we setup the Jenkins pipeline. -- 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]
