You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tajo.apache.org by "JaeHwa Jung (JIRA)" <ji...@apache.org> on 2013/11/18 12:51:21 UTC

[jira] [Resolved] (TAJO-313) Support deprecated variables in CatalogConstants.

     [ https://issues.apache.org/jira/browse/TAJO-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

JaeHwa Jung resolved TAJO-313.
------------------------------

    Resolution: Fixed

Thanks Jihoon.
I've committed now. :)

> Support deprecated variables in CatalogConstants.
> -------------------------------------------------
>
>                 Key: TAJO-313
>                 URL: https://issues.apache.org/jira/browse/TAJO-313
>             Project: Tajo
>          Issue Type: Sub-task
>          Components: catalog
>    Affects Versions: 0.8-incubating
>            Reporter: JaeHwa Jung
>            Assignee: JaeHwa Jung
>            Priority: Minor
>             Fix For: 0.8-incubating
>
>         Attachments: TAJO-313.patch, TAJO-313_2.patch, TAJO-313_3.patch, TAJO-313_4.patch
>
>
> I renamed JDBC variables in CatalogConstants at [TAJO-297|https://issues.apache.org/jira/browse/TAJO-297]. But I think that some users may use deprecated JDBC variables. So, Tajo should supports deprecated JDBC variables in CatalogConstants.  



--
This message was sent by Atlassian JIRA
(v6.1#6144)