[ 
https://issues.apache.org/jira/browse/HIVE-26049?focusedWorklogId=744547&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-744547
 ]

ASF GitHub Bot logged work on HIVE-26049:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 19/Mar/22 01:49
            Start Date: 19/Mar/22 01:49
    Worklog Time Spent: 10m 
      Work Description: kovjanos commented on pull request #3119:
URL: https://github.com/apache/hive/pull/3119#issuecomment-1072915735


   The upgrade script was adjusted for MSSQL and MYSQL as these engines lost 
the NOT NULL constraint on ALTER. The others - Derby, Postgres and Oracle - 
don't need this, actually this would be invalid ALTER statement for those 
engines.


-- 
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: gitbox-unsubscr...@hive.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 744547)
    Time Spent: 0.5h  (was: 20m)

> Inconsistent TBL_NAME lengths in HMS schema 
> --------------------------------------------
>
>                 Key: HIVE-26049
>                 URL: https://issues.apache.org/jira/browse/HIVE-26049
>             Project: Hive
>          Issue Type: Bug
>          Components: Database/Schema
>    Affects Versions: 4.0.0-alpha-1
>            Reporter: Janos Kovacs
>            Assignee: Janos Kovacs
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The transaction specific tables have TBL_NAME length set to 128 while the 
> TBLS itself allows 256. When a table is created with such a long name hive 
> fails e.g. to lock the table.
> TBL_NAME needs to be consistent across the whole schema.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to