[jira] [Commented] (TRAFODION-1706) trafodion is not compatible with hbase 1.0 and later version

2016-04-01 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/TRAFODION-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15222459#comment-15222459
 ] 

ASF GitHub Bot commented on TRAFODION-1706:
---

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-trafodion/pull/411


> trafodion is not compatible with hbase 1.0 and later version
> 
>
> Key: TRAFODION-1706
> URL: https://issues.apache.org/jira/browse/TRAFODION-1706
> Project: Apache Trafodion
>  Issue Type: Bug
>Reporter: mashengchen
>Assignee: mashengchen
>
> trafodion is not compatible with hbase 1.0 and later version.Some api is 
> changed, like Hlog was changed to WAL...



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

[jira] [Commented] (TRAFODION-1915) support adding/retrieving comments to SQL objects

2016-04-01 Thread Roberta Marton (JIRA) 

[ 
https://issues.apache.org/jira/browse/TRAFODION-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15222392#comment-15222392
 ] 

Roberta Marton commented on TRAFODION-1915:
---

Just to expand a bit on Qifan's suggestion.  Here are some things to consider 
to incorporate comments into Trafodion DDL.

The first step it to see what Oracle and other SQL vendors support and define 
externals for specifying, accessing, and changing comments on objects, columns, 
etc.

Once the externals are completed, then changes are needed:

-> In the sql parser to accept the new syntax for all affected existing and new 
statements

->In DDL code that creates and drops objects to detect comments and, either 
store comment details in existing metadata or remove them.  The comment feature 
should not require any metadata structure changes if we store comments in the 
system metadata table called TEXT as suggested by Qifan.  This would avoid an 
upgrade procedure.

->In DDL code that adds mechanisms to add, delete, or update comments.

->In DDL code that supports access comments.  We can display it as part of a 
SHOWDDL statement, use a UDR,  and perhaps supporting something like "get 
comments on table mytable".

->In other parts of the code depending on how much we decide to integrate 
comments.  For example, should we cache comments related to objects in our 
metadata cache, etc?  If so, then we support things like cache query 
invalidation when comments change.

As mentioned above, this support can be added incrementally. For example, 
comment support can be added initially for tables and columns.  Later, it can 
be expanded to schemas, udrs, views, or other object where it makes sense.

There is a bit of work required to add this feature but overall fairly straight 
forward to implement and isolated from other features.
It would be a good project for someone who wants to understand how Trafodion 
DDL works.


> support adding/retrieving comments to SQL objects
> -
>
> Key: TRAFODION-1915
> URL: https://issues.apache.org/jira/browse/TRAFODION-1915
> Project: Apache Trafodion
>  Issue Type: New Feature
>Reporter: liu ming
>Priority: Minor
>
> It is desired to have compatible capability of Oracle's syntax to add/get 
> comments to SQL objects, like tables and columns, etc.
> QiFan give a very good initial design for this:
> 1.add a new type for column TEXT_TYPE in meta-table 
> TRAFODION."_MD_".TEXT, say COMMENT_TYPE;
> 2.allow COMMENT ON syntax in the parser;
> 3.convert the content of COMMENT ON stmt into insertion/update of a 
> row(s) in the TEXT meta-data table for the SQL object in question;
> 4.write a UDF to show the comment easily for a SQL object, by hiding the 
> join of the meta-data TEXT and OBJECTS table.
> Can be done increamentally since there are a lot of SQL objects. And multiple 
> changes to different components.



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

[jira] [Commented] (TRAFODION-1913) org.trafodion.jdbc.t4 throws an error

2016-04-01 Thread Selvaganesan Govindarajan (JIRA) 

[ 
https://issues.apache.org/jira/browse/TRAFODION-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15222369#comment-15222369
 ] 

Selvaganesan Govindarajan commented on TRAFODION-1913:
--

Analyzing the core file shows the following:

There are 27 columns requested in the scan.
This scan returned 17 rows
Most of the rows have only 12 columns.
One row had 4 columns and another had 11 columns.

13th row returned 4 columns only. It is not clear if the cells are missing from 
the table. You need to check in the raw hbase table.  The missing column in 
Trafodion triggers filling up the data with the default values. But the column 
has been defined with no default value.  Hence Trafodion dumped core. We will 
use this JIRA to return an internal error instead of dumping core.


>  org.trafodion.jdbc.t4 throws an error
> --
>
> Key: TRAFODION-1913
> URL: https://issues.apache.org/jira/browse/TRAFODION-1913
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: client-jdbc-t4
>Affects Versions: 1.3-incubating
>Reporter: Pierre Smits
>Assignee: Selvaganesan Govindarajan
> Attachments: hs_err_pid50530.log
>
>
> After a restart of both the Trafodion 1.3 Sandbox and Apache ofbiz I get the 
> subject of this posting returned in the OFBiz log. The excerpt shows:
>  [java] Caused by: org.trafodion.jdbc.t4.HPT4Exception: The message id: 
> problem_with_server_read
>  [java] at 
> org.trafodion.jdbc.t4.HPT4Messages.createSQLException(HPT4Messages.java:304) 
> ~[jdbcT4.jar:?]
>  [java] at org.trafodion.jdbc.t4.InputOutput.doIO(InputOutput.java:373) 
> ~[jdbcT4.jar:?]
>  [java] at 
> org.trafodion.jdbc.t4.T4Connection.getReadBuffer(T4Connection.java:154) 
> ~[jdbcT4.jar:?]
>  [java] at 
> org.trafodion.jdbc.t4.T4Connection.EndTransaction(T4Connection.java:398) 
> ~[jdbcT4.jar:?]
>  [java] at 
> org.trafodion.jdbc.t4.InterfaceConnection.endTransaction(InterfaceConnection.java:1222)
>  ~[jdbcT4.jar:?]
>  [java] at 
> org.trafodion.jdbc.t4.InterfaceConnection.rollback(InterfaceConnection.java:440)
>  ~[jdbcT4.jar:?]
>  [java] at 
> org.trafodion.jdbc.t4.TrafT4Connection.rollback(TrafT4Connection.java:1025) 
> ~[jdbcT4.jar:?]
> This continued multiple times until the OFBiz instantiation halts.



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

[jira] [Assigned] (TRAFODION-1913) org.trafodion.jdbc.t4 throws an error

2016-04-01 Thread Selvaganesan Govindarajan (JIRA) 

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

Selvaganesan Govindarajan reassigned TRAFODION-1913:


Assignee: Selvaganesan Govindarajan

>  org.trafodion.jdbc.t4 throws an error
> --
>
> Key: TRAFODION-1913
> URL: https://issues.apache.org/jira/browse/TRAFODION-1913
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: client-jdbc-t4
>Affects Versions: 1.3-incubating
>Reporter: Pierre Smits
>Assignee: Selvaganesan Govindarajan
> Attachments: hs_err_pid50530.log
>
>
> After a restart of both the Trafodion 1.3 Sandbox and Apache ofbiz I get the 
> subject of this posting returned in the OFBiz log. The excerpt shows:
>  [java] Caused by: org.trafodion.jdbc.t4.HPT4Exception: The message id: 
> problem_with_server_read
>  [java] at 
> org.trafodion.jdbc.t4.HPT4Messages.createSQLException(HPT4Messages.java:304) 
> ~[jdbcT4.jar:?]
>  [java] at org.trafodion.jdbc.t4.InputOutput.doIO(InputOutput.java:373) 
> ~[jdbcT4.jar:?]
>  [java] at 
> org.trafodion.jdbc.t4.T4Connection.getReadBuffer(T4Connection.java:154) 
> ~[jdbcT4.jar:?]
>  [java] at 
> org.trafodion.jdbc.t4.T4Connection.EndTransaction(T4Connection.java:398) 
> ~[jdbcT4.jar:?]
>  [java] at 
> org.trafodion.jdbc.t4.InterfaceConnection.endTransaction(InterfaceConnection.java:1222)
>  ~[jdbcT4.jar:?]
>  [java] at 
> org.trafodion.jdbc.t4.InterfaceConnection.rollback(InterfaceConnection.java:440)
>  ~[jdbcT4.jar:?]
>  [java] at 
> org.trafodion.jdbc.t4.TrafT4Connection.rollback(TrafT4Connection.java:1025) 
> ~[jdbcT4.jar:?]
> This continued multiple times until the OFBiz instantiation halts.



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

[jira] [Created] (TRAFODION-1916) dcscheck fails with cdh5.4.4 and hbase 1.0.0

2016-04-01 Thread Arvind Narain (JIRA) 
Arvind Narain created TRAFODION-1916:


 Summary: dcscheck fails with cdh5.4.4 and hbase 1.0.0
 Key: TRAFODION-1916
 URL: https://issues.apache.org/jira/browse/TRAFODION-1916
 Project: Apache Trafodion
  Issue Type: Bug
  Components: connectivity-dcs
Affects Versions: 2.0-incubating
 Environment: cdh5.4.4 and hbase 1.0.0
Reporter: Arvind Narain


After TRAFODION-1706 got checked in ( support for vanila hbase 1.0 and cdh 
1.0.0-cdh5.4.4) seeing the following error while running dcscheck:

[ERROR] Terminal initialization failed; falling back to unsupported
java.lang.IncompatibleClassChangeError: Found class jline.Terminal, but 
interface was expected
at jline.TerminalFactory.create(TerminalFactory.java:101)
at jline.TerminalFactory.get(TerminalFactory.java:158)
at jline.console.ConsoleReader.(ConsoleReader.java:229)
at jline.console.ConsoleReader.(ConsoleReader.java:221)
at jline.console.ConsoleReader.(ConsoleReader.java:209)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at org.apache.zookeeper.ZooKeeperMain.run(ZooKeeperMain.java:311)
at org.apache.zookeeper.ZooKeeperMain.main(ZooKeeperMain.java:282)

Zookeeper listen port: 30770
DcsMaster listen port: 1459538608929]

Active DcsMaster: "localhost", pid 18447

Process Configured  Actual  Down
-   --  --  
DcsMaster   1   1   
DcsServer   1   1   
mxosrvr 4   4   

-

Earlier with DCS subsystem zookeeper-3.4.5.jar  and related jars used to get 
installed in $DCS_INSTALL_DIR/lib. 

With TRAFODION-1828 ( DCS - Remove unneeded dependent jars) some of these got 
eliminated. Now "bin/dcs zkcli" command ( similar to hbase zkcli) picks up the 
corresponding zookeeper jar from CDH environment.

With the current environment (cdh5.4.4/hbase 1.0.0) this error is seen.

One workaround would be to package the zookeeper jar along with DCS.

Error seen because of incompatibility between jline and jline2. Some solutions 
on the web are to:

1. export HADOOP_USER_CLASSPATH_FIRST=true
2. ".. users should backup and remove the jline-0.9.94.jar file ... "

Above suggestions need to be checked to see if they solve the issue seen with 
dcscheck.



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

[jira] [Commented] (TRAFODION-1706) trafodion is not compatible with hbase 1.0 and later version

2016-04-01 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/TRAFODION-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1599#comment-1599
 ] 

ASF GitHub Bot commented on TRAFODION-1706:
---

GitHub user DaveBirdsall opened a pull request:

https://github.com/apache/incubator-trafodion/pull/411

[TRAFODION-1706] Update executor/TEST020 expected results

I noticed that the regression test executor/TEST020 was failing this 
morning. It might have been due to last night's merge of #367 but this is not 
certain. In any case, this will fix it.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/DaveBirdsall/incubator-trafodion 
FixRegressions

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-trafodion/pull/411.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #411


commit ff76b2a686ae3087165976dee0ab6ff7853f6ffa
Author: Dave Birdsall 
Date:   2016-04-01T20:24:13Z

[TRAFODION-1706] Update executor/TEST020 expected results




> trafodion is not compatible with hbase 1.0 and later version
> 
>
> Key: TRAFODION-1706
> URL: https://issues.apache.org/jira/browse/TRAFODION-1706
> Project: Apache Trafodion
>  Issue Type: Bug
>Reporter: mashengchen
>Assignee: mashengchen
>
> trafodion is not compatible with hbase 1.0 and later version.Some api is 
> changed, like Hlog was changed to WAL...



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

[jira] [Updated] (TRAFODION-1915) support adding/retrieving comments to SQL objects

2016-04-01 Thread liu ming (JIRA) 

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

liu ming updated TRAFODION-1915:

Priority: Minor  (was: Major)

> support adding/retrieving comments to SQL objects
> -
>
> Key: TRAFODION-1915
> URL: https://issues.apache.org/jira/browse/TRAFODION-1915
> Project: Apache Trafodion
>  Issue Type: New Feature
>Reporter: liu ming
>Priority: Minor
>
> It is desired to have compatible capability of Oracle's syntax to add/get 
> comments to SQL objects, like tables and columns, etc.
> QiFan give a very good initial design for this:
> 1.add a new type for column TEXT_TYPE in meta-table 
> TRAFODION."_MD_".TEXT, say COMMENT_TYPE;
> 2.allow COMMENT ON syntax in the parser;
> 3.convert the content of COMMENT ON stmt into insertion/update of a 
> row(s) in the TEXT meta-data table for the SQL object in question;
> 4.write a UDF to show the comment easily for a SQL object, by hiding the 
> join of the meta-data TEXT and OBJECTS table.
> Can be done increamentally since there are a lot of SQL objects. And multiple 
> changes to different components.



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

[jira] [Created] (TRAFODION-1915) support adding/retrieving comments to SQL objects

2016-04-01 Thread liu ming (JIRA) 
liu ming created TRAFODION-1915:
---

 Summary: support adding/retrieving comments to SQL objects
 Key: TRAFODION-1915
 URL: https://issues.apache.org/jira/browse/TRAFODION-1915
 Project: Apache Trafodion
  Issue Type: New Feature
Reporter: liu ming


It is desired to have compatible capability of Oracle's syntax to add/get 
comments to SQL objects, like tables and columns, etc.

QiFan give a very good initial design for this:
1.  add a new type for column TEXT_TYPE in meta-table 
TRAFODION."_MD_".TEXT, say COMMENT_TYPE;
2.  allow COMMENT ON syntax in the parser;
3.  convert the content of COMMENT ON stmt into insertion/update of a 
row(s) in the TEXT meta-data table for the SQL object in question;
4.  write a UDF to show the comment easily for a SQL object, by hiding the 
join of the meta-data TEXT and OBJECTS table.


Can be done increamentally since there are a lot of SQL objects. And multiple 
changes to different components.



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