hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rui Li (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-14412) Add a timezone-aware timestamp
Date Wed, 10 Aug 2016 02:02:20 GMT

    [ https://issues.apache.org/jira/browse/HIVE-14412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15414594#comment-15414594
] 

Rui Li commented on HIVE-14412:
-------------------------------

The error is {{Invalid JDK version in profile 'doclint-java8-disable': Unbounded range [1.8,
for project net.schmizz:sshj}}. It happens when we run
{code}
cd hive/testutils/ptest2
mvn clean package -DskipTests -Drat.numUnapprovedLicenses=1000 -Dmaven.repo.local=/home/jenkins/jenkins-slave/workspace/PreCommit-HIVE-MASTER-Build/.m2
{code}
I found the following in the pom of sshj-0.10.1-SNAPSHOT
{code}
        <profile>
            <id>doclint-java8-disable</id>
            <activation>
                <jdk>[1.8,</jdk>
            </activation>
            <build>
                <plugins>
                    <plugin>
                        <groupId>org.apache.maven.plugins</groupId>
                        <artifactId>maven-javadoc-plugin</artifactId>
                        <configuration>
                            <additionalparam>-Xdoclint:none</additionalparam>
                        </configuration>
                    </plugin>
                </plugins>
            </build>
        </profile>
{code}

But like I said, I can't reproduce the error locally with maven 3.3.9.

> Add a timezone-aware timestamp
> ------------------------------
>
>                 Key: HIVE-14412
>                 URL: https://issues.apache.org/jira/browse/HIVE-14412
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Hive
>            Reporter: Rui Li
>            Assignee: Rui Li
>         Attachments: HIVE-14412.1.patch, HIVE-14412.1.patch
>
>
> Java's Timestamp stores the time elapsed since the epoch. While it's by itself unambiguous,
ambiguity comes when we parse a string into timestamp, or convert a timestamp to string, causing
problems like HIVE-14305.
> To solve the issue, I think we should make timestamp aware of timezone.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message