March 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4724) Allow support for vdb.ddl in the .vdb files

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4724?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4724: --------------------------------------- We'll need a doc change for this as well, since it currently implies that the zip is only for vdb.xml. > Allow support for vdb.ddl in the .vdb files > ------------------------------------------- > > Key: TEIID-4724 > URL: https://issues.jboss.org/browse/TEIID-4724 > Project: Teiid > Issue Type: Enhancement > Components: VDB > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Alpaha1 > Fix For: 9.3 > > > With the DDL based metadata, ".vdb" file archive should allow to contain a "vdb.ddl" file that can be deployed. Based on TEIID-4719 this needs to allow to load metadata from INDEX and DDL-FILE metadata repositories. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4523) CXF is not used by Salesforce BulkConnection

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4523?page=com.atlassian.jira.plugin... ] Ramesh Reddy edited comment on TEIID-4523 at 3/8/17 3:26 PM: ------------------------------------------------------------- It is becoming difficult to see which library will be used when dealing with 34 version. SF library is bad such that some methods use config.createTransport().connect() like Line 390 in BulkConnection and some do as [~shawkins] mentions. was (Author: rareddy): It is becoming difficult to see which library will be used when dealing with 34 version. Should we fork? > CXF is not used by Salesforce BulkConnection > -------------------------------------------- > > Key: TEIID-4523 > URL: https://issues.jboss.org/browse/TEIID-4523 > Project: Teiid > Issue Type: Bug > Components: Salesforce Connector > Affects Versions: 8.12 > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 9.3 > > > TEIID-3493 added the CXF transport, but it's not used by the salesforce BulkConnection. In v22 they make use of a static call, so we won't make a change there. With 34 we can extend the SalesforceConnectorConfig createConnection - but a HttpURLConnection is expected so this may not be straight-forward. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2167) Permissions should also specify object type

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2167?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2167: --------------------------------------- It's in the docs and is defined by DataPolicy.ResourceType. Will you want something beyond that? > Permissions should also specify object type > ------------------------------------------- > > Key: TEIID-2167 > URL: https://issues.jboss.org/browse/TEIID-2167 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.3 > > > Teiid permissions only specify a resource name. However it is possible to have to have conflicting schema/table (since we are using non-sql safe unquoted names) or table/procedure names. > Ideally we would use proper sql names (this is true everywhere, not just in permissions) and specify the object type (TABLE, PROCEDURE, SCHEMA, LANGUAGE, FUNCTION, etc.). This would also allow us to have a more standard USAGE permission, rather than something like LANGUAGE, which is used to convey the permission and object type. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4523) CXF is not used by Salesforce BulkConnection

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4523?page=com.atlassian.jira.plugin... ] Ramesh Reddy edited comment on TEIID-4523 at 3/8/17 3:10 PM: ------------------------------------------------------------- It is becoming difficult to see which library will be used when dealing with 34 version. Should we fork? was (Author: rareddy): It is becoming difficult to see which library will be used when dealing with 34 version. IMO, we should create extended classes for each. > CXF is not used by Salesforce BulkConnection > -------------------------------------------- > > Key: TEIID-4523 > URL: https://issues.jboss.org/browse/TEIID-4523 > Project: Teiid > Issue Type: Bug > Components: Salesforce Connector > Affects Versions: 8.12 > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 9.3 > > > TEIID-3493 added the CXF transport, but it's not used by the salesforce BulkConnection. In v22 they make use of a static call, so we won't make a change there. With 34 we can extend the SalesforceConnectorConfig createConnection - but a HttpURLConnection is expected so this may not be straight-forward. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2167) Permissions should also specify object type

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIID-2167?page=com.atlassian.jira.plugin... ] Barry LaFond commented on TEIID-2167: ------------------------------------- Implementing functionality that provides either user interaction or setting the type automatically will both required a complete set of allowable types. Can these types be provided somehow through an API? > Permissions should also specify object type > ------------------------------------------- > > Key: TEIID-2167 > URL: https://issues.jboss.org/browse/TEIID-2167 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.3 > > > Teiid permissions only specify a resource name. However it is possible to have to have conflicting schema/table (since we are using non-sql safe unquoted names) or table/procedure names. > Ideally we would use proper sql names (this is true everywhere, not just in permissions) and specify the object type (TABLE, PROCEDURE, SCHEMA, LANGUAGE, FUNCTION, etc.). This would also allow us to have a more standard USAGE permission, rather than something like LANGUAGE, which is used to convey the permission and object type. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4523) CXF is not used by Salesforce BulkConnection

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4523?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4523: ------------------------------------- It is becoming difficult to see which library will be used when dealing with 34 version. IMO, we should create extended classes for each. > CXF is not used by Salesforce BulkConnection > -------------------------------------------- > > Key: TEIID-4523 > URL: https://issues.jboss.org/browse/TEIID-4523 > Project: Teiid > Issue Type: Bug > Components: Salesforce Connector > Affects Versions: 8.12 > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 9.3 > > > TEIID-3493 added the CXF transport, but it's not used by the salesforce BulkConnection. In v22 they make use of a static call, so we won't make a change there. With 34 we can extend the SalesforceConnectorConfig createConnection - but a HttpURLConnection is expected so this may not be straight-forward. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4523) CXF is not used by Salesforce BulkConnection

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4523?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4523: --------------------------------------- To add more detail: See HttpURLConnection connection = config.createConnection(url, null); on line 558 of BulkConnection. That does give us the ability to override the createConnection handling using our SalesforceConnectorConfig class. However it doesn't look like CXF provides an abstraction for getting just an HttpURLConnection. If not, then the BulkConnection logic would need to be rewritten. Since this has not come up as a community or product issue, I'd say we push it for now if you don't see an easy way to address it. > CXF is not used by Salesforce BulkConnection > -------------------------------------------- > > Key: TEIID-4523 > URL: https://issues.jboss.org/browse/TEIID-4523 > Project: Teiid > Issue Type: Bug > Components: Salesforce Connector > Affects Versions: 8.12 > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 9.3 > > > TEIID-3493 added the CXF transport, but it's not used by the salesforce BulkConnection. In v22 they make use of a static call, so we won't make a change there. With 34 we can extend the SalesforceConnectorConfig createConnection - but a HttpURLConnection is expected so this may not be straight-forward. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4523) CXF is not used by Salesforce BulkConnection

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4523?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-4523: ----------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) > CXF is not used by Salesforce BulkConnection > -------------------------------------------- > > Key: TEIID-4523 > URL: https://issues.jboss.org/browse/TEIID-4523 > Project: Teiid > Issue Type: Bug > Components: Salesforce Connector > Affects Versions: 8.12 > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 9.3 > > > TEIID-3493 added the CXF transport, but it's not used by the salesforce BulkConnection. In v22 they make use of a static call, so we won't make a change there. With 34 we can extend the SalesforceConnectorConfig createConnection - but a HttpURLConnection is expected so this may not be straight-forward. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4733) Streamline JDG integration

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4733?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-4733: -------------------------------- Fix Version/s: 9.3 > Streamline JDG integration > -------------------------- > > Key: TEIID-4733 > URL: https://issues.jboss.org/browse/TEIID-4733 > Project: Teiid > Issue Type: Feature Request > Components: JDG Connector > Reporter: Van Halbert > Assignee: Ramesh Reddy > Fix For: 9.3 > > > This jira is to discuss the issues based on current design that inhibit the ability to stream line JDG integration and/or to recommend changes that would enable the use/access of a JDG cache in an automated way. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4787) Add Netzza datasource configuration example

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4787?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-4787. --------------------------------- Resolution: Duplicate Issue Duplicate TEIID-3862 > Add Netzza datasource configuration example > -------------------------------------------- > > Key: TEIID-4787 > URL: https://issues.jboss.org/browse/TEIID-4787 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Connector > Reporter: Ramesh Reddy > Fix For: 9.3 > > > In "docs" directory there is no example for Netezza datasource. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2017