[JBoss JIRA] (TEIID-2626) If a column type is not set, null values will be written into persisted batches
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2626?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2626.
---------------------------------
> If a column type is not set, null values will be written into persisted batches
> -------------------------------------------------------------------------------
>
> Key: TEIID-2626
> URL: https://issues.jboss.org/browse/TEIID-2626
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.5
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Blocker
> Fix For: 8.4.1, 8.5
>
>
> The buffer manager will choose the null serializer if a column type is not set. This is not expected to happen, but test code can be sloppy which isn't evident if the weak reference cache is working effectively.
> However there is one place in the code that is effected, which is the internally generated partitionId column on any window function expression with a non-empty over clause. This means that on systems with limited memory and or poor performing weak references no results for the window function may be returned.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (TEIID-2625) Part of join criteria is getting ignored
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2625?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2625.
---------------------------------
> Part of join criteria is getting ignored
> ----------------------------------------
>
> Key: TEIID-2625
> URL: https://issues.jboss.org/browse/TEIID-2625
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.7.1
> Environment: z/OS JZOS
> Reporter: Jeff Hayes
> Assignee: Steven Hawkins
> Attachments: 7.7_Teiid_SHOWPLAN
>
>
> The second part of the join criteria (and CHORUS_J0.userid = CHORUS_B.evtuserid) appears to be getting ignored. The result has same results as when only the first criteria (CHORUS_J0.sysid = cx2.sysid) is provided.
> Same query works are 8.1 with query plan listing both criteria in joinNode however for 7.7 only shows first criteria.
>
> Please see attached query plan.
> One thing to note is that the same query on 7.7 works when the databases
> are on DB2 (using DB2 translator) but not when they are on Datacom (different translator). Is this possibly a translator issue maybe not being able to support multiple join criteria?
> 8/15: Confirmed the problem occurs for both DB2 and Datacom translators.
> Any advice would be appreciated as this is affected a customer installation.
> Thanks!
> Jeff
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months