You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sentry.apache.org by "SentryQA (JIRA)" <ji...@apache.org> on 2014/05/23 22:57:01 UTC
[jira] [Commented] (SENTRY-229) SentrySchemaTool initSchema does
not work with postgres 8.1and oracle
[ https://issues.apache.org/jira/browse/SENTRY-229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007693#comment-14007693 ]
SentryQA commented on SENTRY-229:
---------------------------------
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12646603/SENTRY-229.2.patch against master.
{color:red}Overall:{color} -1 due to an error
{color:red}ERROR:{color} failed to build with patch (exit code 1)
Console output: http://bigtop01.cloudera.org:8080/job/PreCommit-SENTRY-Build/84/console
This message is automatically generated.
> SentrySchemaTool initSchema does not work with postgres 8.1and oracle
> ---------------------------------------------------------------------
>
> Key: SENTRY-229
> URL: https://issues.apache.org/jira/browse/SENTRY-229
> Project: Sentry
> Issue Type: Bug
> Reporter: Arun Suresh
> Assignee: Arun Suresh
> Attachments: SENTRY-229.1.patch, SENTRY-229.2.patch
>
>
> The initSchema routine cribs stating that it cannot 'SET client_encoding' to UTF8.. This works fine on postgres 9.2
> In the case of oracle, There seems to be an identifier that is longer than 30 character.
--
This message was sent by Atlassian JIRA
(v6.2#6252)