[JBoss JIRA] (TEIID-5991) Excel limit combined with predicates can produce wrong results
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5991?page=com.atlassian.jira.plugi... ]
Steven Hawkins resolved TEIID-5991.
-----------------------------------
Resolution: Done
The simplest solution is just to remove the translator based limit handling - at the worst there is some additional projection that is occurring.
> Excel limit combined with predicates can produce wrong results
> --------------------------------------------------------------
>
> Key: TEIID-5991
> URL: https://issues.redhat.com/browse/TEIID-5991
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 15.0, 13.1.2, 14.0.1
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> A query such as "select FirstName, ROW_ID from Sheet1 where ROW_ID != 15 LIMIT 1,3" against the test names.xls will produce 2 rows as a result when 3 are expected. This is because the row limit and where predicate are applied conjunctively, rather than the limit on top of the predicate result.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (TEIID-5991) Excel limit combined with predicates can produce wrong results
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5991?focusedWorklogId=12451730&pag... ]
Steven Hawkins logged work on TEIID-5991:
-----------------------------------------
Author: Steven Hawkins
Created on: 14/Jul/20 12:03 PM
Start Date: 14/Jul/20 12:03 PM
Worklog Time Spent: 1 hour, 30 minutes
Issue Time Tracking
-------------------
Remaining Estimate: 2 hours, 30 minutes (was: 4 hours)
Time Spent: 1 hour, 30 minutes
Worklog Id: (was: 12451730)
> Excel limit combined with predicates can produce wrong results
> --------------------------------------------------------------
>
> Key: TEIID-5991
> URL: https://issues.redhat.com/browse/TEIID-5991
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 15.0, 13.1.2, 14.0.1
>
> Original Estimate: 4 hours
> Time Spent: 1 hour, 30 minutes
> Remaining Estimate: 2 hours, 30 minutes
>
> A query such as "select FirstName, ROW_ID from Sheet1 where ROW_ID != 15 LIMIT 1,3" against the test names.xls will produce 2 rows as a result when 3 are expected. This is because the row limit and where predicate are applied conjunctively, rather than the limit on top of the predicate result.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (TEIID-5991) Excel limit combined with predicates can produce wrong results
by Steven Hawkins (Jira)
Steven Hawkins created TEIID-5991:
-------------------------------------
Summary: Excel limit combined with predicates can produce wrong results
Key: TEIID-5991
URL: https://issues.redhat.com/browse/TEIID-5991
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 15.0, 13.1.2, 14.0.1
A query such as "select FirstName, ROW_ID from Sheet1 where ROW_ID != 15 LIMIT 1,3" against the test names.xls will produce 2 rows as a result when 3 are expected. This is because the row limit and where predicate are applied conjunctively, rather than the limit on top of the predicate result.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (TEIID-5928) Allow External and Internal materialization of multi-source to fail/update individually
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5928?page=com.atlassian.jira.plugi... ]
Steven Hawkins updated TEIID-5928:
----------------------------------
Original Estimate: 1 day, 4 hours (was: 0 minutes)
> Allow External and Internal materialization of multi-source to fail/update individually
> ---------------------------------------------------------------------------------------
>
> Key: TEIID-5928
> URL: https://issues.redhat.com/browse/TEIID-5928
> Project: Teiid
> Issue Type: Enhancement
> Components: Common
> Affects Versions: 12.2.2
> Reporter: Rafael Sampaio
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 15.0
>
> Original Estimate: 1 day, 4 hours
> Time Spent: 30 minutes
> Remaining Estimate: 0 minutes
>
> Hi, all.
> First of all thanks in advance for your attention, and efforts on such a great product.
> Since I haven't found any docs or examples regarding my current usage (please if this already exists or there's a better way of doing this, disregard this request and advice) here goes my suggestion:
> It would be nice to have a way to gracefully update/fail per source, if a view that has Materialization enabled and target a multi-source source model, because things can get, messy if I have to create a view per source and Materialize each one and only then create a unified (UNION) view.
> Using this approach also obligates me to implement custom insert/update/delete/based on the discriminator column.
> Thanks again.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (TEIID-5989) Retrieve metadata omitted with TEIID-5815
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5989?focusedWorklogId=12451726&pag... ]
Steven Hawkins logged work on TEIID-5989:
-----------------------------------------
Author: Steven Hawkins
Created on: 13/Jul/20 3:10 PM
Start Date: 13/Jul/20 3:10 PM
Worklog Time Spent: 30 minutes
Issue Time Tracking
-------------------
Remaining Estimate: 0 minutes (was: 30 minutes)
Time Spent: 30 minutes
Worklog Id: (was: 12451726)
> Retrieve metadata omitted with TEIID-5815
> -----------------------------------------
>
> Key: TEIID-5989
> URL: https://issues.redhat.com/browse/TEIID-5989
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 15.0, 13.1.2, 14.0.1
>
> Original Estimate: 30 minutes
> Time Spent: 30 minutes
> Remaining Estimate: 0 minutes
>
> We need the retrieve extension metadata to know when to use the retrieve method.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (TEIID-5989) Retrieve metadata omitted with TEIID-5815
by Steven Hawkins (Jira)
Steven Hawkins created TEIID-5989:
-------------------------------------
Summary: Retrieve metadata omitted with TEIID-5815
Key: TEIID-5989
URL: https://issues.redhat.com/browse/TEIID-5989
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 15.0, 13.1.2, 14.0.1
We need the retrieve extension metadata to know when to use the retrieve method.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (TEIID-5986) S3 translator flat file parser can not support unicode
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5986?focusedWorklogId=12451725&pag... ]
Steven Hawkins logged work on TEIID-5986:
-----------------------------------------
Author: Steven Hawkins
Created on: 13/Jul/20 2:31 PM
Start Date: 13/Jul/20 2:31 PM
Worklog Time Spent: 30 minutes
Work Description: Time spent corresponding with Rui and making the small change.
Issue Time Tracking
-------------------
Remaining Estimate: 0 minutes (was: 30 minutes)
Time Spent: 30 minutes
Worklog Id: (was: 12451725)
> S3 translator flat file parser can not support unicode
> ------------------------------------------------------
>
> Key: TEIID-5986
> URL: https://issues.redhat.com/browse/TEIID-5986
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Reporter: Rui Wang
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 15.0
>
> Original Estimate: 30 minutes
> Time Spent: 30 minutes
> Remaining Estimate: 0 minutes
>
> I saw there is one ticket on Unicode support for flat file. Seems I can not config it in V14 if I am using java api to create my VDB xml. Steven mentioned it is migrated to S3 translater. Could you pls enhance it in latest Teiid version
>
> [https://issues.redhat.com/browse/TEIID-4340?page=com.atlassian.jira.plugi...]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months