[jira] [Created] (HIVE-23927) Cast to Timestamp generates different output for Integer & Float values
Renukaprasad C created HIVE-23927: - Summary: Cast to Timestamp generates different output for Integer & Float values Key: HIVE-23927 URL: https://issues.apache.org/jira/browse/HIVE-23927 Project: Hive Issue Type: Bug Reporter: Renukaprasad C Double consider the input value as SECOND and converts into Millis internally. Whereas, Integer value will be considered as Millis and produce different output. org.apache.hadoop.hive.serde2.objectinspector.primitive.PrimitiveObjectInspectorUtils.getTimestamp(Object, PrimitiveObjectInspector, boolean) - Handles Integral & Decimal values differently. This cause the issue. 0: jdbc:hive2://localhost:1> select cast(1.204135216E9 as timestamp) Double2TimeStamp, cast(1204135216 as timestamp) Int2TimeStamp from abc tablesample(1 rows); OK INFO : Compiling command(queryId=renu_20200724140642_70132390-ee12-4214-a2ca-a7e10556fc14): select cast(1.204135216E9 as timestamp) Double2TimeStamp, cast(1204135216 as timestamp) Int2TimeStamp from abc tablesample(1 rows) INFO : Concurrency mode is disabled, not creating a lock manager INFO : Semantic Analysis Completed (retrial = false) INFO : Returning Hive schema: Schema(fieldSchemas:[FieldSchema(name:double2timestamp, type:timestamp, comment:null), FieldSchema(name:int2timestamp, type:timestamp, comment:null)], properties:null) INFO : Completed compiling command(queryId=renu_20200724140642_70132390-ee12-4214-a2ca-a7e10556fc14); Time taken: 0.175 seconds INFO : Concurrency mode is disabled, not creating a lock manager INFO : Executing command(queryId=renu_20200724140642_70132390-ee12-4214-a2ca-a7e10556fc14): select cast(1.204135216E9 as timestamp) Double2TimeStamp, cast(1204135216 as timestamp) Int2TimeStamp from abc tablesample(1 rows) INFO : Completed executing command(queryId=renu_20200724140642_70132390-ee12-4214-a2ca-a7e10556fc14); Time taken: 0.001 seconds INFO : OK INFO : Concurrency mode is disabled, not creating a lock manager ++--+ |double2timestamp| int2timestamp | ++--+ | 2008-02-27 18:00:16.0 | 1970-01-14 22:28:55.216 | ++--+ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HIVE-23583) Fix CVE-2020-1945: Apache Ant insecure temporary file vulnerability by updating to latest ANT
Renukaprasad C created HIVE-23583: - Summary: Fix CVE-2020-1945: Apache Ant insecure temporary file vulnerability by updating to latest ANT Key: HIVE-23583 URL: https://issues.apache.org/jira/browse/HIVE-23583 Project: Hive Issue Type: Bug Affects Versions: 3.1.2 Reporter: Renukaprasad C Assignee: Renukaprasad C Fix For: 4.0.0 Update ANT to fix: CVE-2020-1945: Apache Ant insecure temporary file vulnerability Severity: Medium Vendor: The Apache Software Foundation Versions Affected: Apache Ant 1.1 to 1.9.14 and 1.10.0 to 1.10.7 Description: Apache Ant uses the default temporary directory identified by the Java system property java.io.tmpdir for several tasks and may thus leak sensitive information. The fixcrlf and replaceregexp tasks also copy files from the temporary directory back into the build tree allowing an attacker to inject modified source files into the build process. Mitigation: Ant users of versions 1.1 to 1.9.14 and 1.10.0 to 1.10.7 should set the java.io.tmpdir system property to point to a directory only readable and writable by the current user prior to running Ant. Users of versions 1.9.15 and 1.10.8 can use the Ant property ant.tmpfile instead. Users of Ant 1.10.8 can rely on Ant protecting the temporary files if the underlying filesystem allows it, but we still recommend using a private temporary directory instead. References: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-1945 https://nvd.nist.gov/vuln/detail/CVE-2020-1945 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HIVE-22932) Unable to kill Beeline with Ctrl+C
Renukaprasad C created HIVE-22932: - Summary: Unable to kill Beeline with Ctrl+C Key: HIVE-22932 URL: https://issues.apache.org/jira/browse/HIVE-22932 Project: Hive Issue Type: Bug Reporter: Renukaprasad C Stopped the server and tried to stop the beeline console with "Ctrl+C". But it unable to kill the process & gets process gets hanged. Read call got blocked. Attached the thread dump. 0: jdbc:hive2://localhost:1> show tables; Unknown HS2 problem when communicating with Thrift server. Error: org.apache.thrift.transport.TTransportException: java.net.SocketException: Broken pipe (state=08S01,code=0) 0: jdbc:hive2://localhost:1> Interrupting... Please be patient this may take some time. Interrupting... Please be patient this may take some time. Interrupting... Please be patient this may take some time. Interrupting... Please be patient this may take some time. Interrupting... Please be patient this may take some time. Interrupting... Please be patient this may take some time. Interrupting... Please be patient this may take some time. Interrupting... Please be patient this may take some time. Interrupting... Please be patient this may take some time. Interrupting... Please be patient this may take some time. Interrupting... Please be patient this may take some time. Interrupting... Please be patient this may take some time. Interrupting... Please be patient this may take some time. Interrupting... Please be patient this may take some time. Interrupting... Please be patient this may take some time. Interrupting... Please be patient this may take some time. Interrupting... Please be patient this may take some time. Interrupting... Please be patient this may take some time. 2020-02-26 17:40:42 Full thread dump Java HotSpot(TM) 64-Bit Server VM (25.72-b15 mixed mode): "NonBlockingInputStreamThread" #16 daemon prio=5 os_prio=0 tid=0x7f0318c10800 nid=0x258c in Object.wait() [0x7f031c193000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0xfe9113c0> (a jline.internal.NonBlockingInputStream) at jline.internal.NonBlockingInputStream.run(NonBlockingInputStream.java:278) - locked <0xfe9113c0> (a jline.internal.NonBlockingInputStream) at java.lang.Thread.run(Thread.java:745) "Service Thread" #11 daemon prio=9 os_prio=0 tid=0x7f032006c000 nid=0x257b runnable [0x] java.lang.Thread.State: RUNNABLE "C1 CompilerThread3" #10 daemon prio=9 os_prio=0 tid=0x7f0320060800 nid=0x257a waiting on condition [0x] java.lang.Thread.State: RUNNABLE "C2 CompilerThread2" #9 daemon prio=9 os_prio=0 tid=0x7f0320056000 nid=0x2579 waiting on condition [0x] java.lang.Thread.State: RUNNABLE "C2 CompilerThread1" #8 daemon prio=9 os_prio=0 tid=0x7f0320054000 nid=0x2578 waiting on condition [0x] java.lang.Thread.State: RUNNABLE "C2 CompilerThread0" #7 daemon prio=9 os_prio=0 tid=0x7f0320051000 nid=0x2577 waiting on condition [0x] java.lang.Thread.State: RUNNABLE "JDWP Event Helper Thread" #6 daemon prio=10 os_prio=0 tid=0x7f032004f000 nid=0x2576 runnable [0x] java.lang.Thread.State: RUNNABLE "JDWP Transport Listener: dt_socket" #5 daemon prio=10 os_prio=0 tid=0x7f032004b800 nid=0x2575 runnable [0x] java.lang.Thread.State: RUNNABLE "Signal Dispatcher" #4 daemon prio=9 os_prio=0 tid=0x7f0320035800 nid=0x2574 waiting on condition [0x] java.lang.Thread.State: RUNNABLE "Finalizer" #3 daemon prio=8 os_prio=0 tid=0x7f0320003800 nid=0x2572 in Object.wait() [0x7f0324b1c000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0xfe930770> (a java.lang.ref.ReferenceQueue$Lock) at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:143) - locked <0xfe930770> (a java.lang.ref.ReferenceQueue$Lock) at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:164) at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:209) "Reference Handler" #2 daemon prio=10 os_prio=0 tid=0x006a6000 nid=0x2571 in Object.wait() [0x7f0324c1d000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0xfe9307b0> (a java.lang.ref.Reference$Lock) at java.lang.Object.wait(Object.java:502) at java.lang.ref.Reference.tryHandlePending(Reference.java:191) - locked <0xfe9307b0> (a java.lang.ref.Reference$Lock) at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:153) "main" #1 prio=5 os_prio=0 tid=0x00628800 nid=0x2567 runnable [0x7f033a60b000]
[jira] [Created] (HIVE-22887) MR Job cannot set custom OutputCommitter during job execution.
Renukaprasad C created HIVE-22887: - Summary: MR Job cannot set custom OutputCommitter during job execution. Key: HIVE-22887 URL: https://issues.apache.org/jira/browse/HIVE-22887 Project: Hive Issue Type: Bug Reporter: Renukaprasad C Assignee: Renukaprasad C MapRedTask set jobs OutputCommitter to NullOutputCommitter. org.apache.hadoop.hive.ql.io.HiveFileFormatUtils.prepareJobOutput(JobConf) this sets the OutputCommitter to NullOutputCommitter always. conf.setOutputCommitter(NullOutputCommitter.class); There are some cases where we need to customize the OutputCommitter. Like on SUCCESS, they need to write some file or do some custom operation in theie own OutputCommitter If someone wants to provide their own OutputCommitter then its not possible in the current implementation. Related issues: MR - MAPREDUCE-1802, Hive - HIVE-1355. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HIVE-22845) Code compilation fails on Windows when user name begins with 'N' or 'R'
Renukaprasad C created HIVE-22845: - Summary: Code compilation fails on Windows when user name begins with 'N' or 'R' Key: HIVE-22845 URL: https://issues.apache.org/jira/browse/HIVE-22845 Project: Hive Issue Type: Bug Reporter: Renukaprasad C Assignee: Renukaprasad C package-info.java is generated from the script - saveVersion.sh. Generated contetnt is as follows. /* * Generated by saveVersion.sh */ @MetastoreVersionAnnotation(version="4.0.0-SNAPSHOT", shortVersion="4.0.0", revision="Unknown", branch="Unknown", user="India enu", date="Thu Feb 6 17:12:46 IST 2020", url="file:///cygdrive/f/hive/code/os/standalone-metastore", srcChecksum="88f3dc17f75ffda6176faa649593b54e") package org.apache.hadoop.hive.metastore.annotation; When user name begings with 'R' (India\Renu), then it get parsed as Carriage Return in between the string and fails compile. Same issue exists with name begins with 'N' also. Whereas compilation is fine with any other user name doesnt contain \r or \n. -- This message was sent by Atlassian Jira (v8.3.4#803005)
