[JBoss JIRA] (TEIID-4629) Offer a ddl solution to replace the vdb.xml
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4629?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4629:
---------------------------------------
For conformance, we should also not have CREATE DATABASE set the current database.
> Offer a ddl solution to replace the vdb.xml
> -------------------------------------------
>
> Key: TEIID-4629
> URL: https://issues.jboss.org/browse/TEIID-4629
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine, Server
> Reporter: Steven Hawkins
> Assignee: Ramesh Reddy
> Fix For: 9.2
>
>
> Based upon the work on TEIID-2578 we should first offer the ability to replace the vdb.xml with ddl. We can additionally include some of the work to represent additional pieces of the vdb as api level metadata objects (instead of in the admin layer) where possible. Ideally this should support as much alter functionality as possible.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (TEIID-4476) Upgrade Cassandra Client library
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4476?page=com.atlassian.jira.plugin... ]
Steven Hawkins reassigned TEIID-4476:
-------------------------------------
Assignee: Kylin Soong
This is slightly more involved that I had hoped, so it may get pushed to 9.3 if needed.
It looks like we should use the shaded version of the dependency to include a specific netty version. The current cassandra resource adapter doesn't include netty at all, so then again it may not be needed.
The metrics-core version should be updated to 3.1.2, but will need to added to the nexus repository as it only goes up to 3.0.2.
It seems ok to leave off the jnr dependencies.
The code related to the version should switch to using the Cassandra VersionNumber, as discussed in TEIID-4213
[~vijaynm] is this similar to your assessment from TEIID-4723
> Upgrade Cassandra Client library
> --------------------------------
>
> Key: TEIID-4476
> URL: https://issues.jboss.org/browse/TEIID-4476
> Project: Teiid
> Issue Type: Task
> Components: Misc. Connectors
> Reporter: Ramesh Reddy
> Assignee: Kylin Soong
> Fix For: 9.2
>
>
> Cassandra client version of the library is 2.1, this needs to be upgraded to the latest version.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (TEIID-4629) Offer a ddl solution to replace the vdb.xml
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4629?page=com.atlassian.jira.plugin... ]
Ramesh Reddy edited comment on TEIID-4629 at 1/25/17 2:05 PM:
--------------------------------------------------------------
Cool, for some reason I thought we removed it. We just need to make sure implicit context setting has been removed then.
> Offer a ddl solution to replace the vdb.xml
> -------------------------------------------
>
> Key: TEIID-4629
> URL: https://issues.jboss.org/browse/TEIID-4629
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine, Server
> Reporter: Steven Hawkins
> Assignee: Ramesh Reddy
> Fix For: 9.2
>
>
> Based upon the work on TEIID-2578 we should first offer the ability to replace the vdb.xml with ddl. We can additionally include some of the work to represent additional pieces of the vdb as api level metadata objects (instead of in the admin layer) where possible. Ideally this should support as much alter functionality as possible.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (TEIID-4629) Offer a ddl solution to replace the vdb.xml
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4629?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4629:
---------------------------------------
It's already there as a ddl/server side construct. The client side handling was removed since DDL was not being issued directly from the client.
> Offer a ddl solution to replace the vdb.xml
> -------------------------------------------
>
> Key: TEIID-4629
> URL: https://issues.jboss.org/browse/TEIID-4629
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine, Server
> Reporter: Steven Hawkins
> Assignee: Ramesh Reddy
> Fix For: 9.2
>
>
> Based upon the work on TEIID-2578 we should first offer the ability to replace the vdb.xml with ddl. We can additionally include some of the work to represent additional pieces of the vdb as api level metadata objects (instead of in the admin layer) where possible. Ideally this should support as much alter functionality as possible.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (TEIID-4536) Support create schema with multiple statements
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4536?page=com.atlassian.jira.plugin... ]
Ramesh Reddy edited comment on TEIID-4536 at 1/25/17 1:49 PM:
--------------------------------------------------------------
Ok, this is only optional considering SET SCHEMA from TEIID-4629, thus your categorization as I see. I will move this off 9.2 then.
I still see as confusing syntax, or cumbersome syntax for one to follow.
was (Author: rareddy):
Ok, this is only optional considering SET SCHEMA from TEIID-4629, thus your categorization as I see. I will move this off 9.2 then.
> Support create schema with multiple statements
> ----------------------------------------------
>
> Key: TEIID-4536
> URL: https://issues.jboss.org/browse/TEIID-4536
> Project: Teiid
> Issue Type: Sub-task
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Minor
> Fix For: 9.2
>
>
> Create schema can support following create statements being directly associated rather than requiring an intermediate use schema
> create schema x
> create view ...
> ...
> ;
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (TEIID-4629) Offer a ddl solution to replace the vdb.xml
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4629?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-4629:
-------------------------------------
OK, we need to bring back SET SCHEMA command then.
> Offer a ddl solution to replace the vdb.xml
> -------------------------------------------
>
> Key: TEIID-4629
> URL: https://issues.jboss.org/browse/TEIID-4629
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine, Server
> Reporter: Steven Hawkins
> Assignee: Ramesh Reddy
> Fix For: 9.2
>
>
> Based upon the work on TEIID-2578 we should first offer the ability to replace the vdb.xml with ddl. We can additionally include some of the work to represent additional pieces of the vdb as api level metadata objects (instead of in the admin layer) where possible. Ideally this should support as much alter functionality as possible.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (TEIID-4051) Swagger metadata includes internal java constructs
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4051?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-4051:
----------------------------------
Fix Version/s: 9.3
(was: 9.2)
> Swagger metadata includes internal java constructs
> --------------------------------------------------
>
> Key: TEIID-4051
> URL: https://issues.jboss.org/browse/TEIID-4051
> Project: Teiid
> Issue Type: Quality Risk
> Components: Server
> Affects Versions: 8.12.x
> Reporter: Steven Hawkins
> Fix For: 9.3
>
>
> From IntegrationTestRestWarGeneration the swagger metadata includes definitions for Statement, ResultSet, StreamingOutput, etc.:
> ...
> InputStream:
> type: "object"
> Statement:
> type: "object"
> properties:
> queryTimeout:
> type: "integer"
> format: "int32"
> closed:
> type: "boolean"
> default: false
> resultSet:
> $ref: "#/definitions/ResultSet"
> ...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months