[JBoss JIRA] (TEIID-5898) Wrong force-wsc jar in translator / force.api module 41
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5898?page=com.atlassian.jira.plugi... ]
Steven Hawkins updated TEIID-5898:
----------------------------------
Fix Version/s: 7.6-13.0.2
> Wrong force-wsc jar in translator / force.api module 41
> -------------------------------------------------------
>
> Key: TEIID-5898
> URL: https://issues.redhat.com/browse/TEIID-5898
> Project: Teiid
> Issue Type: Bug
> Components: Build/Kits
> Affects Versions: 12.2
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 13.1, 12.3.2, 13.0.3, 7.6-13.0.2
>
> Original Estimate: 4 hours
> Time Spent: 4 hours
> Remaining Estimate: 0 minutes
>
> For some reason between 12.1 and 12.2 the wrong force-wsc began to be picked up in the 41 translator. This was not due to TEIID-5713 as the 12.1.2 kit is correct, so this was likely introduced by the wildfly related refactoring (but it's not clear why).
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (TEIIDSB-168) Translator is not found if given name does not match translatorName
by Ramesh Reddy (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-168?focusedWorklogId=12450053&pa... ]
Ramesh Reddy logged work on TEIIDSB-168:
----------------------------------------
Author: Ramesh Reddy
Created on: 06/Feb/20 12:58 PM
Start Date: 06/Feb/20 12:58 PM
Worklog Time Spent: 4 hours
Issue Time Tracking
-------------------
Remaining Estimate: 0 minutes
Time Spent: 4 hours
Worklog Id: (was: 12450053)
> Translator is not found if given name does not match translatorName
> -------------------------------------------------------------------
>
> Key: TEIIDSB-168
> URL: https://issues.redhat.com/browse/TEIIDSB-168
> Project: Teiid Spring Boot
> Issue Type: Bug
> Components: core
> Affects Versions: 1.0.0
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Priority: Blocker
> Fix For: 1.4.0
>
> Time Spent: 4 hours
> Remaining Estimate: 0 minutes
>
> When vdb-code-generator tries to verify the translator name to the dependencies section, it is trying to match the external source name to the translator name. In case if there are multiple sources available for a translator like sqlserver (jtds, mssqlserver) the names will not align.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (TEIIDSB-168) Translator is not found if given name does not match translatorName
by Ramesh Reddy (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-168?page=com.atlassian.jira.plug... ]
Ramesh Reddy resolved TEIIDSB-168.
----------------------------------
Resolution: Done
Added a way to look up a translator by its name also by the source name. Fixed NPE by checking the GAV before we can use it.
> Translator is not found if given name does not match translatorName
> -------------------------------------------------------------------
>
> Key: TEIIDSB-168
> URL: https://issues.redhat.com/browse/TEIIDSB-168
> Project: Teiid Spring Boot
> Issue Type: Bug
> Components: core
> Affects Versions: 1.0.0
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Priority: Blocker
> Fix For: 1.4.0
>
>
> When vdb-code-generator tries to verify the translator name to the dependencies section, it is trying to match the external source name to the translator name. In case if there are multiple sources available for a translator like sqlserver (jtds, mssqlserver) the names will not align.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (TEIID-5900) query with local and remote pushes too much to remote
by Ken Geis (Jira)
Ken Geis created TEIID-5900:
-------------------------------
Summary: query with local and remote pushes too much to remote
Key: TEIID-5900
URL: https://issues.redhat.com/browse/TEIID-5900
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 12.3.1
Reporter: Ken Geis
Assignee: Steven Hawkins
I have a table "A" in an Oracle database. I have a date dimension "B" in Teiid, which is a materialized view of a recursive query. The date dimension has all dates from 1950 to 2050, 36890 rows in total.
I run the following query:
{code:sql}
SELECT *
FROM a
JOIN b
ON a.date_column = b.date_key
{code}
Teiid sends a query to Oracle, which I will paraphrase as:
{code:sql}
SELECT <columns>
FROM a
WHERE date_column IN (to_date('1950-01-01 00:00:00', 'YYYY-MM-DD HH24:MI:SS'),
<36899 other date values!>)
{code}
Oracle breaks either with the length of the query or the number of options in the IN clause.
I thought that MAKEDEP/MAKENOTDEP/MAKEIND could help, but they didn't seem to change anything.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (TEIIDSB-161) Excessive warning about spring.teiid.model.package
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-161?page=com.atlassian.jira.plug... ]
Steven Hawkins updated TEIIDSB-161:
-----------------------------------
Fix Version/s: 1.4.x
> Excessive warning about spring.teiid.model.package
> --------------------------------------------------
>
> Key: TEIIDSB-161
> URL: https://issues.redhat.com/browse/TEIIDSB-161
> Project: Teiid Spring Boot
> Issue Type: Bug
> Components: core
> Reporter: Steven Hawkins
> Priority: Minor
> Fix For: 1.4.x
>
>
> when using a vdb project the warning:
> {code}
> 2020-01-17 17:03:22.491 WARN 6870 --- [ main] o.t.spring.autoconfigure.TeiidServer : ***************************************************************
> 2020-01-17 17:03:22.491 WARN 6870 --- [ main] o.t.spring.autoconfigure.TeiidServer : "spring.teiid.model.package" is NOT set, If you are using any custom translators, it is advised to that this property is set.
> 2020-01-17 17:03:22.491 WARN 6870 --- [ main] o.t.spring.autoconfigure.TeiidServer : consider setting this property to avoid time consuming scanning
> 2020-01-17 17:03:22.491 WARN 6870 --- [ main] o.t.spring.autoconfigure.TeiidServer : ***************************************************************
> {code}
> Seems unnecessary. Also what does it have to do with custom translators?
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (TEIID-5898) Wrong force-wsc jar in translator / force.api module 41
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5898?focusedWorklogId=12450047&pag... ]
Steven Hawkins logged work on TEIID-5898:
-----------------------------------------
Author: Steven Hawkins
Created on: 05/Feb/20 1:47 PM
Start Date: 05/Feb/20 1:47 PM
Worklog Time Spent: 4 hours
Issue Time Tracking
-------------------
Remaining Estimate: 0 minutes (was: 4 hours)
Time Spent: 4 hours
Worklog Id: (was: 12450047)
> Wrong force-wsc jar in translator / force.api module 41
> -------------------------------------------------------
>
> Key: TEIID-5898
> URL: https://issues.redhat.com/browse/TEIID-5898
> Project: Teiid
> Issue Type: Bug
> Components: Build/Kits
> Affects Versions: 12.2
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 13.1, 12.3.2, 13.0.3
>
> Original Estimate: 4 hours
> Time Spent: 4 hours
> Remaining Estimate: 0 minutes
>
> For some reason between 12.1 and 12.2 the wrong force-wsc began to be picked up in the 41 translator. This was not due to TEIID-5713 as the 12.1.2 kit is correct, so this was likely introduced by the wildfly related refactoring (but it's not clear why).
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (TEIID-5898) Wrong force-wsc jar in translator / force.api module 41
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5898?page=com.atlassian.jira.plugi... ]
Steven Hawkins resolved TEIID-5898.
-----------------------------------
Resolution: Done
Added an explicit dependency to the 41 translator to override the managed dependency version that was taking precedent.
> Wrong force-wsc jar in translator / force.api module 41
> -------------------------------------------------------
>
> Key: TEIID-5898
> URL: https://issues.redhat.com/browse/TEIID-5898
> Project: Teiid
> Issue Type: Bug
> Components: Build/Kits
> Affects Versions: 12.2
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 13.1, 12.3.2, 13.0.3
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> For some reason between 12.1 and 12.2 the wrong force-wsc began to be picked up in the 41 translator. This was not due to TEIID-5713 as the 12.1.2 kit is correct, so this was likely introduced by the wildfly related refactoring (but it's not clear why).
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (TEIID-5897) Update srcclr.yml to on 1.0.x branch to run -Prelease profile
by Van Halbert (Jira)
[ https://issues.redhat.com/browse/TEIID-5897?focusedWorklogId=12450046&pag... ]
Van Halbert logged work on TEIID-5897:
--------------------------------------
Author: Van Halbert
Created on: 05/Feb/20 1:32 PM
Start Date: 05/Feb/20 1:32 PM
Worklog Time Spent: 2 hours
Issue Time Tracking
-------------------
Remaining Estimate: 0 minutes (was: 8 minutes)
Time Spent: 2 hours
Worklog Id: (was: 12450046)
> Update srcclr.yml to on 1.0.x branch to run -Prelease profile
> -------------------------------------------------------------
>
> Key: TEIID-5897
> URL: https://issues.redhat.com/browse/TEIID-5897
> Project: Teiid
> Issue Type: Quality Risk
> Components: Build/Kits
> Reporter: Van Halbert
> Assignee: Van Halbert
> Priority: Blocker
> Original Estimate: 8 minutes
> Time Spent: 2 hours
> Remaining Estimate: 0 minutes
>
> Update the 1.0.x branch srcclr.yml file so that source clear runs the -Prelease profile and the same dependencies are analyzed that are included when the -Prelease profile is run when the code is released.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month