[ https://issues.apache.org/jira/browse/HIVE-21455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16796200#comment-16796200 ]
Hive QA commented on HIVE-21455: -------------------------------- Here are the results of testing the latest attachment: https://issues.apache.org/jira/secure/attachment/12962836/HIVE-21455.patch {color:red}ERROR:{color} -1 due to build exiting with an error Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/16573/testReport Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/16573/console Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-16573/ Messages: {noformat} Executing org.apache.hive.ptest.execution.TestCheckPhase Executing org.apache.hive.ptest.execution.PrepPhase Tests exited with: NonZeroExitCodeException Command 'bash /data/hiveptest/working/scratch/source-prep.sh' failed with exit status 1 and output '+ date '+%Y-%m-%d %T.%3N' 2019-03-19 15:28:47.035 + [[ -n /usr/lib/jvm/java-8-openjdk-amd64 ]] + export JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64 + JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64 + export PATH=/usr/lib/jvm/java-8-openjdk-amd64/bin/:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games + PATH=/usr/lib/jvm/java-8-openjdk-amd64/bin/:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games + export 'ANT_OPTS=-Xmx1g -XX:MaxPermSize=256m ' + ANT_OPTS='-Xmx1g -XX:MaxPermSize=256m ' + export 'MAVEN_OPTS=-Xmx1g ' + MAVEN_OPTS='-Xmx1g ' + cd /data/hiveptest/working/ + tee /data/hiveptest/logs/PreCommit-HIVE-Build-16573/source-prep.txt + [[ false == \t\r\u\e ]] + mkdir -p maven ivy + [[ git = \s\v\n ]] + [[ git = \g\i\t ]] + [[ -z master ]] + [[ -d apache-github-source-source ]] + [[ ! -d apache-github-source-source/.git ]] + [[ ! -d apache-github-source-source ]] + date '+%Y-%m-%d %T.%3N' 2019-03-19 15:28:47.038 + cd apache-github-source-source + git fetch origin + git reset --hard HEAD HEAD is now at 36bd89d HIVE-16924 : Support distinct in presence of Group By (Miklos Gergely via Zoltan Haindrich) + git clean -f -d Removing standalone-metastore/metastore-server/src/gen/ + git checkout master Already on 'master' Your branch is up-to-date with 'origin/master'. + git reset --hard origin/master HEAD is now at 36bd89d HIVE-16924 : Support distinct in presence of Group By (Miklos Gergely via Zoltan Haindrich) + git merge --ff-only origin/master Already up-to-date. + date '+%Y-%m-%d %T.%3N' 2019-03-19 15:28:47.700 + rm -rf ../yetus_PreCommit-HIVE-Build-16573 + mkdir ../yetus_PreCommit-HIVE-Build-16573 + git gc + cp -R . ../yetus_PreCommit-HIVE-Build-16573 + mkdir /data/hiveptest/logs/PreCommit-HIVE-Build-16573/yetus + patchCommandPath=/data/hiveptest/working/scratch/smart-apply-patch.sh + patchFilePath=/data/hiveptest/working/scratch/build.patch + [[ -f /data/hiveptest/working/scratch/build.patch ]] + chmod +x /data/hiveptest/working/scratch/smart-apply-patch.sh + /data/hiveptest/working/scratch/smart-apply-patch.sh /data/hiveptest/working/scratch/build.patch error: a/ql/src/java/org/apache/hadoop/hive/ql/io/avro/AvroGenericRecordReader.java: does not exist in index error: patch failed: ql/src/java/org/apache/hadoop/hive/ql/io/avro/AvroGenericRecordReader.java:134 Falling back to three-way merge... Applied patch to 'ql/src/java/org/apache/hadoop/hive/ql/io/avro/AvroGenericRecordReader.java' with conflicts. Going to apply patch with: git apply -p1 error: patch failed: ql/src/java/org/apache/hadoop/hive/ql/io/avro/AvroGenericRecordReader.java:134 Falling back to three-way merge... Applied patch to 'ql/src/java/org/apache/hadoop/hive/ql/io/avro/AvroGenericRecordReader.java' with conflicts. U ql/src/java/org/apache/hadoop/hive/ql/io/avro/AvroGenericRecordReader.java + result=1 + '[' 1 -ne 0 ']' + rm -rf yetus_PreCommit-HIVE-Build-16573 + exit 1 ' {noformat} This message is automatically generated. ATTACHMENT ID: 12962836 - PreCommit-HIVE-Build > Too verbose logging in AvroGenericRecordReader > ---------------------------------------------- > > Key: HIVE-21455 > URL: https://issues.apache.org/jira/browse/HIVE-21455 > Project: Hive > Issue Type: Improvement > Components: HiveServer2 > Affects Versions: 1.2.0, 1.1.0, 2.0.0, 2.1.0, 3.0.0, 3.1.0 > Reporter: Miklos Szurap > Assignee: Miklos Szurap > Priority: Minor > Attachments: HIVE-21455.patch > > > {{AvroGenericRecordReader}} logs the Avro schema for each datafile. It is too > verbose, likely we don't need to log that on INFO level. > For example a table: > {noformat} > create table avro_tbl (c1 string, c2 int, c3 float) stored as avro; > {noformat} > and querying it with a select star - with 3 datafiles HiveServer2 logs the > following: > {noformat} > 2019-03-15 09:18:35,999 INFO org.apache.hadoop.mapred.FileInputFormat: > [HiveServer2-Handler-Pool: Thread-64]: Total input paths to process : 3 > 2019-03-15 09:18:35,999 INFO > org.apache.hadoop.hive.ql.io.avro.AvroGenericRecordReader: > [HiveServer2-Handler-Pool: Thread-64]: Found the avro schema in the job: > {"type":"record","name":"avro_tbl","namespace":"test","fields":[{"name":"c1","type":["null","string"],"default":null},{"name":"c2","type":["null","int"],"default":null},{"name":"c3","type":["null","float"],"default":null}]} > 2019-03-15 09:18:36,004 INFO > org.apache.hadoop.hive.ql.io.avro.AvroGenericRecordReader: > [HiveServer2-Handler-Pool: Thread-64]: Found the avro schema in the job: > {"type":"record","name":"avro_tbl","namespace":"test","fields":[{"name":"c1","type":["null","string"],"default":null},{"name":"c2","type":["null","int"],"default":null},{"name":"c3","type":["null","float"],"default":null}]} > 2019-03-15 09:18:36,010 INFO > org.apache.hadoop.hive.ql.io.avro.AvroGenericRecordReader: > [HiveServer2-Handler-Pool: Thread-64]: Found the avro schema in the job: > {"type":"record","name":"avro_tbl","namespace":"test","fields":[{"name":"c1","type":["null","string"],"default":null},{"name":"c2","type":["null","int"],"default":null},{"name":"c3","type":["null","float"],"default":null}]} > {noformat} > This has a huge performance and storage penalty on a table with big schema > and thousands of datafiles. -- This message was sent by Atlassian JIRA (v7.6.3#76005)