[JBoss JIRA] (TEIID-1131) Document/expand sequence support
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-1131?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-1131:
---------------------------------------
> Does DatabaseMetadata give import facilities for the sequences?
Only pg, and even that is an undocumented feature.
> Document/expand sequence support
> --------------------------------
>
> Key: TEIID-1131
> URL: https://issues.jboss.org/browse/TEIID-1131
> Project: Teiid
> Issue Type: Feature Request
> Components: JDBC Connector, Query Engine
> Affects Versions: 7.0
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 10.0
>
>
> Currently sequence workaround logic only exists for oracle and is undocumented. We should look at expanding sequence support - even for dynamic vdbs, see SQuriel's handling of system queries for retrieving sequence metadata.
> At least allowing the workaround logic to work for all sources that support sequences (Postgres, DB2, etc.) would be good.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (TEIID-1131) Document/expand sequence support
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-1131?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-1131:
-------------------------------------
Does DatabaseMetadata give import facilities for the sequences? We just need to focus from that angle here IMO.
> Document/expand sequence support
> --------------------------------
>
> Key: TEIID-1131
> URL: https://issues.jboss.org/browse/TEIID-1131
> Project: Teiid
> Issue Type: Feature Request
> Components: JDBC Connector, Query Engine
> Affects Versions: 7.0
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 10.0
>
>
> Currently sequence workaround logic only exists for oracle and is undocumented. We should look at expanding sequence support - even for dynamic vdbs, see SQuriel's handling of system queries for retrieving sequence metadata.
> At least allowing the workaround logic to work for all sources that support sequences (Postgres, DB2, etc.) would be good.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (TEIID-1131) Document/expand sequence support
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-1131?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-1131:
---------------------------------------
In addition to lacking type information the hibernate sequence support (with the exception of h2) provides only the name, not the schema nor catalog. That doesn't match very well with our import semantics either.
> Document/expand sequence support
> --------------------------------
>
> Key: TEIID-1131
> URL: https://issues.jboss.org/browse/TEIID-1131
> Project: Teiid
> Issue Type: Feature Request
> Components: JDBC Connector, Query Engine
> Affects Versions: 7.0
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 10.0
>
>
> Currently sequence workaround logic only exists for oracle and is undocumented. We should look at expanding sequence support - even for dynamic vdbs, see SQuriel's handling of system queries for retrieving sequence metadata.
> At least allowing the workaround logic to work for all sources that support sequences (Postgres, DB2, etc.) would be good.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (TEIID-1131) Document/expand sequence support
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-1131?page=com.atlassian.jira.plugin... ]
Steven Hawkins edited comment on TEIID-1131 at 9/27/17 10:55 AM:
-----------------------------------------------------------------
The import above will only work for pg - oracle support was removed from the driver. The other sources need specific metadata queries to retrieve the sequences. So for full support we'd need to add additional import logic with name patterns etc. to pull the names/datatype of the sequences. We could expand our hibernate integration to get at that information - except it doesn't provide the type, so we'd have to assume long.
was (Author: shawkins):
The import above will only work for pg/oracle. The other sources need specific metadata queries to retrieve the sequences. So for full support we'd need to add additional import logic with name patterns etc. to pull the names/datatype of the sequences. We could expand our hibernate integration to get at that information - except it doesn't provide the type, so we'd have to assume long.
> Document/expand sequence support
> --------------------------------
>
> Key: TEIID-1131
> URL: https://issues.jboss.org/browse/TEIID-1131
> Project: Teiid
> Issue Type: Feature Request
> Components: JDBC Connector, Query Engine
> Affects Versions: 7.0
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 10.0
>
>
> Currently sequence workaround logic only exists for oracle and is undocumented. We should look at expanding sequence support - even for dynamic vdbs, see SQuriel's handling of system queries for retrieving sequence metadata.
> At least allowing the workaround logic to work for all sources that support sequences (Postgres, DB2, etc.) would be good.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (TEIID-5082) Salesforce default URL incorrect
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5082?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5082.
-----------------------------------
Resolution: Done
Corrected the URL and added a version check - which is just a warning, but it could be expanded to throw an exception in cases where we know that the api is incompatible and results in what appears to be hung queries.
> Salesforce default URL incorrect
> --------------------------------
>
> Key: TEIID-5082
> URL: https://issues.jboss.org/browse/TEIID-5082
> Project: Teiid
> Issue Type: Bug
> Components: Salesforce Connector
> Affects Versions: 9.2
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 10.0, 9.3.4, 9.2.6
>
>
> With the feature pack kitting changes the 34 url ended up in the 22 resource adapter. That needs to be corrected. Also we need to add a warning on version mismatch as most situations do not work as expected.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (TEIID-5081) FORMATTIMESTAMP is not pushed down to postgresql but formattimestamp is
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5081?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5081.
-----------------------------------
Fix Version/s: 10.0
9.3.4
Resolution: Done
Corrected the check in the compatibility visitor that was checking for timestamp method name suffix in a case sensitive manner.
> FORMATTIMESTAMP is not pushed down to postgresql but formattimestamp is
> -----------------------------------------------------------------------
>
> Key: TEIID-5081
> URL: https://issues.jboss.org/browse/TEIID-5081
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Environment: * teiid 9.3.3
> * jdbc driver: postgresql-9.4.1212.jre7.jar
> * PostgreSQL 9.6.2 on x86_64-pc-linux-gnu, compiled by gcc (Debian 4.9.2-10) 4.9.2, 64-bit
> * java 1.8.0_141-b15
> Reporter: Fábio Franco
> Assignee: Steven Hawkins
> Fix For: 10.0, 9.3.4
>
>
> FORMATTIMESTAMP (uppercase) is NOT pushed to postgres but formattimestamp (lowercase) is correctly pushed.
> FORMATTIMESTAMP (uppercase) plan:
> {code}
> ProjectNode
> + Relational Node ID:0
> + Output Columns:expr1 (string)
> + Statistics:
> 0: Node Output Rows: 1
> 1: Node Next Batch Process Time: 1
> 2: Node Cumulative Next Batch Process Time: 2
> 3: Node Cumulative Process Time: 23
> 4: Node Next Batch Calls: 2
> 5: Node Blocks: 1
> + Cost Estimates:Estimated Node Cardinality: 502.0
> + Child 0:
> AccessNode
> + Relational Node ID:1
> + Output Columns:a (timestamp)
> + Statistics:
> 0: Node Output Rows: 1
> 1: Node Next Batch Process Time: 1
> 2: Node Cumulative Next Batch Process Time: 1
> 3: Node Cumulative Process Time: 22
> 4: Node Next Batch Calls: 2
> 5: Node Blocks: 1
> + Cost Estimates:Estimated Node Cardinality: 502.0
> + Query:SELECT g_0.a AS c_0 FROM ds2.test_z AS g_0 LIMIT 502
> + Model Name:ds2
> + Select Columns:FORMATTIMESTAMP(ds2.test_z.a, 'yyyy-mm-dd')
> + Data Bytes Sent:26
> + Planning Time:13
> ============================================================================
> USER COMMAND:
> SELECT FORMATTIMESTAMP(ds2.test_z.a, 'yyyy-mm-dd') FROM ds2.test_z LIMIT 502
>
> ----------------------------------------------------------------------------
> OPTIMIZE:
> SELECT FORMATTIMESTAMP(ds2.test_z.a, 'yyyy-mm-dd') FROM ds2.test_z LIMIT 502
>
> ----------------------------------------------------------------------------
> GENERATE CANONICAL:
> SELECT FORMATTIMESTAMP(ds2.test_z.a, 'yyyy-mm-dd') FROM ds2.test_z LIMIT 502
>
> CANONICAL PLAN:
> TupleLimit(groups=[], props={MAX_TUPLE_LIMIT=502})
> Project(groups=[ds2.test_z], props={PROJECT_COLS=[FORMATTIMESTAMP(ds2.test_z.a, 'yyyy-mm-dd')]})
> Source(groups=[ds2.test_z])
>
>
> ============================================================================
> EXECUTING PlaceAccess
>
> AFTER:
> TupleLimit(groups=[], props={MAX_TUPLE_LIMIT=502})
> Project(groups=[ds2.test_z], props={PROJECT_COLS=[FORMATTIMESTAMP(ds2.test_z.a, 'yyyy-mm-dd')]})
> Access(groups=[ds2.test_z], props={SOURCE_HINT=null, MODEL_ID=Schema name=ds2, nameInSource=null, uuid=tid:15dc08a3b0c7-00018583-00000000})
> Source(groups=[ds2.test_z])
>
>
> ============================================================================
> EXECUTING RaiseAccess
> LOW [Relational Planner] FORMATTIMESTAMP literal parse 'yyyy-mm-dd' not supported by source ds2 - FORMATTIMESTAMP(ds2.test_z.a, 'yyyy-mm-dd') was not pushed
>
> AFTER:
> TupleLimit(groups=[])
> Project(groups=[ds2.test_z], props={PROJECT_COLS=[FORMATTIMESTAMP(ds2.test_z.a, 'yyyy-mm-dd')]})
> Access(groups=[ds2.test_z], props={SOURCE_HINT=null, MODEL_ID=Schema name=ds2, nameInSource=null, uuid=tid:15dc08a3b0c7-00018583-00000000})
> Source(groups=[ds2.test_z])
>
>
> ============================================================================
> EXECUTING AssignOutputElements
>
> AFTER:
> TupleLimit(groups=[], props={MAX_TUPLE_LIMIT=502, OUTPUT_COLS=[FORMATTIMESTAMP(ds2.test_z.a, 'yyyy-mm-dd')]})
> Project(groups=[ds2.test_z], props={PROJECT_COLS=[FORMATTIMESTAMP(ds2.test_z.a, 'yyyy-mm-dd')], OUTPUT_COLS=[FORMATTIMESTAMP(ds2.test_z.a, 'yyyy-mm-dd')]})
> Access(groups=[ds2.test_z], props={SOURCE_HINT=null, MODEL_ID=Schema name=ds2, nameInSource=null, uuid=tid:15dc08a3b0c7-00018583-00000000, OUTPUT_COLS=[ds2.test_z.a]})
> Source(groups=[ds2.test_z], props={OUTPUT_COLS=[ds2.test_z.a]})
>
>
> ============================================================================
> EXECUTING PushLimit
>
> AFTER:
> Project(groups=[ds2.test_z], props={PROJECT_COLS=[FORMATTIMESTAMP(ds2.test_z.a, 'yyyy-mm-dd')], OUTPUT_COLS=[FORMATTIMESTAMP(ds2.test_z.a, 'yyyy-mm-dd')], SOURCE_HINT=null})
> Access(groups=[ds2.test_z], props={SOURCE_HINT=null, MODEL_ID=Schema name=ds2, nameInSource=null, uuid=tid:15dc08a3b0c7-00018583-00000000, OUTPUT_COLS=[ds2.test_z.a]})
> TupleLimit(groups=[], props={MAX_TUPLE_LIMIT=502, OUTPUT_COLS=[ds2.test_z.a]})
> Source(groups=[ds2.test_z], props={OUTPUT_COLS=[ds2.test_z.a]})
>
>
> ============================================================================
> EXECUTING CalculateCost
>
> AFTER:
> Project(groups=[ds2.test_z], props={PROJECT_COLS=[FORMATTIMESTAMP(ds2.test_z.a, 'yyyy-mm-dd')], OUTPUT_COLS=[FORMATTIMESTAMP(ds2.test_z.a, 'yyyy-mm-dd')], SOURCE_HINT=null, EST_CARDINALITY=502.0, EST_COL_STATS={FORMATTIMESTAMP(ds2.test_z.a, 'yyyy-mm-dd')=[502.0, 502.0, 0.0]}})
> Access(groups=[ds2.test_z], props={SOURCE_HINT=null, MODEL_ID=Schema name=ds2, nameInSource=null, uuid=tid:15dc08a3b0c7-00018583-00000000, OUTPUT_COLS=[ds2.test_z.a], EST_CARDINALITY=502.0, EST_COL_STATS={ds2.test_z.a=[502.0, 502.0, 0.0]}})
> TupleLimit(groups=[], props={MAX_TUPLE_LIMIT=502, OUTPUT_COLS=[ds2.test_z.a], EST_CARDINALITY=502.0, EST_COL_STATS={ds2.test_z.a=[502.0, 502.0, 0.0]}})
> Source(groups=[ds2.test_z], props={OUTPUT_COLS=[ds2.test_z.a], EST_COL_STATS={ds2.test_z.a=[-1.0, -1.0, -1.0]}, EST_CARDINALITY=-1.0})
> ============================================================================
> EXECUTING PlanSorts
> AFTER:
> Project(groups=[ds2.test_z])
> Access(groups=[ds2.test_z])
> TupleLimit(groups=[])
> Source(groups=[ds2.test_z])
> ============================================================================
> EXECUTING CollapseSource
> AFTER:
> Project(groups=[ds2.test_z], props={PROJECT_COLS=[FORMATTIMESTAMP(ds2.test_z.a, 'yyyy-mm-dd')], OUTPUT_COLS=[FORMATTIMESTAMP(ds2.test_z.a, 'yyyy-mm-dd')], SOURCE_HINT=null, EST_CARDINALITY=502.0, EST_COL_STATS={FORMATTIMESTAMP(ds2.test_z.a, 'yyyy-mm-dd')=[502.0, 502.0, 0.0]}})
> Access(groups=[ds2.test_z], props={SOURCE_HINT=null, MODEL_ID=Schema name=ds2, nameInSource=null, uuid=tid:15dc08a3b0c7-00018583-00000000, OUTPUT_COLS=[ds2.test_z.a], EST_CARDINALITY=502.0, EST_COL_STATS={ds2.test_z.a=[502.0, 502.0, 0.0]}, ATOMIC_REQUEST=SELECT ds2.test_z.a FROM ds2.test_z LIMIT 502})
> ============================================================================
> CONVERTING PLAN TREE TO PROCESS TREE
> PROCESS PLAN =
> ProjectNode(0) output=[FORMATTIMESTAMP(ds2.test_z.a, 'yyyy-mm-dd')] [FORMATTIMESTAMP(ds2.test_z.a, 'yyyy-mm-dd')]
> AccessNode(1) output=[ds2.test_z.a] SELECT g_0.a AS c_0 FROM ds2.test_z AS g_0 LIMIT 502
> ============================================================================
> ----------------------------------------------------------------------------
> OPTIMIZATION COMPLETE:
> PROCESSOR PLAN:
> ProjectNode(0) output=[FORMATTIMESTAMP(ds2.test_z.a, 'yyyy-mm-dd')] [FORMATTIMESTAMP(ds2.test_z.a, 'yyyy-mm-dd')]
> AccessNode(1) output=[ds2.test_z.a] SELECT g_0.a AS c_0 FROM ds2.test_z AS g_0 LIMIT 502
> ============================================================================
> {code}
> ----
> formattimestamp (lowercase) plan:
> {code}
> AccessNode
> + Relational Node ID:0
> + Output Columns:expr1 (string)
> + Statistics:
> 0: Node Output Rows: 1
> 1: Node Next Batch Process Time: 0
> 2: Node Cumulative Next Batch Process Time: 0
> 3: Node Cumulative Process Time: 3
> 4: Node Next Batch Calls: 2
> 5: Node Blocks: 1
> + Cost Estimates:Estimated Node Cardinality: 502.0
> + Query:SELECT formattimestamp(g_0.a, 'yyyy-mm-dd') AS c_0 FROM ds2.test_z AS g_0 LIMIT 502
> + Model Name:ds2
> + Data Bytes Sent:26
> + Planning Time:3
> ============================================================================
> USER COMMAND:
> SELECT formattimestamp(ds2.test_z.a, 'yyyy-mm-dd') FROM ds2.test_z LIMIT 502
> ----------------------------------------------------------------------------
> OPTIMIZE:
> SELECT formattimestamp(ds2.test_z.a, 'yyyy-mm-dd') FROM ds2.test_z LIMIT 502
> ----------------------------------------------------------------------------
> GENERATE CANONICAL:
> SELECT formattimestamp(ds2.test_z.a, 'yyyy-mm-dd') FROM ds2.test_z LIMIT 502
> CANONICAL PLAN:
> TupleLimit(groups=[], props={MAX_TUPLE_LIMIT=502})
> Project(groups=[ds2.test_z], props={PROJECT_COLS=[formattimestamp(ds2.test_z.a, 'yyyy-mm-dd')]})
> Source(groups=[ds2.test_z])
> ============================================================================
> EXECUTING PlaceAccess
> AFTER:
> TupleLimit(groups=[], props={MAX_TUPLE_LIMIT=502})
> Project(groups=[ds2.test_z], props={PROJECT_COLS=[formattimestamp(ds2.test_z.a, 'yyyy-mm-dd')]})
> Access(groups=[ds2.test_z], props={SOURCE_HINT=null, MODEL_ID=Schema name=ds2, nameInSource=null, uuid=tid:15dc08a3b0c7-00018583-00000000})
> Source(groups=[ds2.test_z])
> ============================================================================
> EXECUTING RaiseAccess
> AFTER:
> Access(groups=[ds2.test_z], props={SOURCE_HINT=null, MODEL_ID=Schema name=ds2, nameInSource=null, uuid=tid:15dc08a3b0c7-00018583-00000000})
> TupleLimit(groups=[], props={MAX_TUPLE_LIMIT=502})
> Project(groups=[ds2.test_z], props={PROJECT_COLS=[formattimestamp(ds2.test_z.a, 'yyyy-mm-dd')]})
> Source(groups=[ds2.test_z])
> ============================================================================
> EXECUTING AssignOutputElements
> AFTER:
> Access(groups=[ds2.test_z], props={SOURCE_HINT=null, MODEL_ID=Schema name=ds2, nameInSource=null, uuid=tid:15dc08a3b0c7-00018583-00000000, OUTPUT_COLS=[formattimestamp(ds2.test_z.a, 'yyyy-mm-dd')]})
> TupleLimit(groups=[], props={MAX_TUPLE_LIMIT=502, OUTPUT_COLS=[formattimestamp(ds2.test_z.a, 'yyyy-mm-dd')]})
> Project(groups=[ds2.test_z], props={PROJECT_COLS=[formattimestamp(ds2.test_z.a, 'yyyy-mm-dd')], OUTPUT_COLS=[formattimestamp(ds2.test_z.a, 'yyyy-mm-dd')]})
> Source(groups=[ds2.test_z], props={OUTPUT_COLS=[ds2.test_z.a]})
> ============================================================================
> EXECUTING PushLimit
> AFTER:
> Access(groups=[ds2.test_z])
> TupleLimit(groups=[])
> Project(groups=[ds2.test_z])
> Source(groups=[ds2.test_z])
> ============================================================================
> EXECUTING CalculateCost
> AFTER:
> Access(groups=[ds2.test_z], props={SOURCE_HINT=null, MODEL_ID=Schema name=ds2, nameInSource=null, uuid=tid:15dc08a3b0c7-00018583-00000000, OUTPUT_COLS=[formattimestamp(ds2.test_z.a, 'yyyy-mm-dd')], EST_CARDINALITY=502.0, EST_COL_STATS={formattimestamp(ds2.test_z.a, 'yyyy-mm-dd')=[502.0, 502.0, 0.0]}})
> TupleLimit(groups=[], props={MAX_TUPLE_LIMIT=502, OUTPUT_COLS=[formattimestamp(ds2.test_z.a, 'yyyy-mm-dd')], EST_CARDINALITY=502.0, EST_COL_STATS={formattimestamp(ds2.test_z.a, 'yyyy-mm-dd')=[502.0, 502.0, 0.0]}})
> Project(groups=[ds2.test_z], props={PROJECT_COLS=[formattimestamp(ds2.test_z.a, 'yyyy-mm-dd')], OUTPUT_COLS=[formattimestamp(ds2.test_z.a, 'yyyy-mm-dd')], EST_CARDINALITY=-1.0})
> Source(groups=[ds2.test_z], props={OUTPUT_COLS=[ds2.test_z.a], EST_COL_STATS={ds2.test_z.a=[-1.0, -1.0, -1.0]}, EST_CARDINALITY=-1.0})
> ============================================================================
> EXECUTING PlanSorts
> AFTER:
> Access(groups=[ds2.test_z])
> TupleLimit(groups=[])
> Project(groups=[ds2.test_z])
> Source(groups=[ds2.test_z])
> ============================================================================
> EXECUTING CollapseSource
> AFTER:
> Access(groups=[ds2.test_z], props={SOURCE_HINT=null, MODEL_ID=Schema name=ds2, nameInSource=null, uuid=tid:15dc08a3b0c7-00018583-00000000, OUTPUT_COLS=[formattimestamp(ds2.test_z.a, 'yyyy-mm-dd')], EST_CARDINALITY=502.0, EST_COL_STATS={formattimestamp(ds2.test_z.a, 'yyyy-mm-dd')=[502.0, 502.0, 0.0]}, ATOMIC_REQUEST=SELECT formattimestamp(ds2.test_z.a, 'yyyy-mm-dd') FROM ds2.test_z LIMIT 502})
> ============================================================================
> CONVERTING PLAN TREE TO PROCESS TREE
> PROCESS PLAN =
> AccessNode(0) output=[formattimestamp(ds2.test_z.a, 'yyyy-mm-dd')] SELECT formattimestamp(g_0.a, 'yyyy-mm-dd') AS c_0 FROM ds2.test_z AS g_0 LIMIT 502
> ============================================================================
> ----------------------------------------------------------------------------
> OPTIMIZATION COMPLETE:
> PROCESSOR PLAN:
> AccessNode(0) output=[formattimestamp(ds2.test_z.a, 'yyyy-mm-dd')] SELECT formattimestamp(g_0.a, 'yyyy-mm-dd') AS c_0 FROM ds2.test_z AS g_0 LIMIT 502
> ============================================================================
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (TEIID-5079) Salesforce issues
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5079?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5079.
-----------------------------------
Resolution: Done
Updated the docs and added the id column to create a well formed query.
> Salesforce issues
> -----------------
>
> Key: TEIID-5079
> URL: https://issues.jboss.org/browse/TEIID-5079
> Project: Teiid
> Issue Type: Bug
> Components: Salesforce Connector
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 10.0
>
>
> In looking into other issue two small salesforce issues cropped up:
> 1. setting modelAuditFields requires using the translator property - the import property is ignored. This also doesn't seem to be documented.
> 2. Creating a join where fields are omitted from the child result in a malformed query:
> SELECT Account.Name FROM Account LEFT OUTER JOIN Contact ON Account.Id = Contact.AccountId
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (TEIID-5083) Deprecate the Salesforce API 22 access
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-5083:
-------------------------------------
Summary: Deprecate the Salesforce API 22 access
Key: TEIID-5083
URL: https://issues.jboss.org/browse/TEIID-5083
Project: Teiid
Issue Type: Task
Components: Salesforce Connector
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 10.0
The salesforce 22 access is quite out of date. Especially with the possible introduction of a newer version, we should deprecate the old.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (TEIID-5082) Salesforce default URL incorrect
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-5082:
-------------------------------------
Summary: Salesforce default URL incorrect
Key: TEIID-5082
URL: https://issues.jboss.org/browse/TEIID-5082
Project: Teiid
Issue Type: Bug
Components: Salesforce Connector
Affects Versions: 9.2
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 10.0, 9.3.4, 9.2.6
With the feature pack kitting changes the 34 url ended up in the 22 resource adapter. That needs to be corrected. Also we need to add a warning on version mismatch as most situations do not work as expected.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months