August 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4300) Soft dead lock between the main reader thread and the cancel thread

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4300?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-4300: ------------------------------------------- Bugzilla References: (was: https://bugzilla.redhat.com/show_bug.cgi?id=1350333) Bugzilla Update: (was: Perform) > Soft dead lock between the main reader thread and the cancel thread > ------------------------------------------------------------------- > > Key: TEIID-4300 > URL: https://issues.jboss.org/browse/TEIID-4300 > Project: Teiid > Issue Type: Bug > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > From Steven's [comment|https://issues.jboss.org/browse/TEIID-3781?focusedCommentId=13255...]: > {quote} > I can see on the client side that there is a soft dead lock between the main reader thread and the cancel thread, such that the synchronization of the cancel method can prevent it from receiving the response. > {quote} > You can find logs and description [here|https://issues.jboss.org/browse/TEIID-3781?focusedCommentId=13254934...]. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4299) Object translator null values correctly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4299?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-4299: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1367925, https://bugzilla.redhat.com/show_bug.cgi?id=1349159 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1349159) > Object translator null values correctly > --------------------------------------- > > Key: TEIID-4299 > URL: https://issues.jboss.org/browse/TEIID-4299 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 9.x, 8.12.5 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Critical > Fix For: 9.1 > > > The object translator wasn't handling the setting of null values when its tried to be set on a native attribute (i.e., long, int, boolean). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4389) Local connection waits for active VDB 1, 000, 000 times longer than specified in waitForLoad property

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4389?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4389. ----------------------------------- Resolution: Done Corrected the logic and added a test. > Local connection waits for active VDB 1,000,000 times longer than specified in waitForLoad property > --------------------------------------------------------------------------------------------------- > > Key: TEIID-4389 > URL: https://issues.jboss.org/browse/TEIID-4389 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver > Affects Versions: 8.12.5 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 9.1, 9.0.3 > > > If user specifies waitForLoad connection property in URL, Teiid waits for longer time than specified in the property. > I believe it is because you call Object.wait(long) method with wrong parameter \[1\]. In combination with TEIID-4388, from users point of view, local connection waits for active VDB for ever. > \[1\] See this [commit|https://github.com/teiid/teiid/commit/d7e161ff04c77f8f2da85b2debb1...]. You call method like _vdb.wait(timeOutNanos);_, but from javadoc: *timeout - the maximum time to wait in milliseconds.* It means that Teiid waits 1,000,000 times longer than specified in parameter. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4389) Local connection waits for active VDB 1, 000, 000 times longer than specified in waitForLoad property

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4389?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4389: ---------------------------------- Component/s: JDBC Driver Fix Version/s: 9.1 9.0.3 > Local connection waits for active VDB 1,000,000 times longer than specified in waitForLoad property > --------------------------------------------------------------------------------------------------- > > Key: TEIID-4389 > URL: https://issues.jboss.org/browse/TEIID-4389 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver > Affects Versions: 8.12.5 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 9.1, 9.0.3 > > > If user specifies waitForLoad connection property in URL, Teiid waits for longer time than specified in the property. > I believe it is because you call Object.wait(long) method with wrong parameter \[1\]. In combination with TEIID-4388, from users point of view, local connection waits for active VDB for ever. > \[1\] See this [commit|https://github.com/teiid/teiid/commit/d7e161ff04c77f8f2da85b2debb1...]. You call method like _vdb.wait(timeOutNanos);_, but from javadoc: *timeout - the maximum time to wait in milliseconds.* It means that Teiid waits 1,000,000 times longer than specified in parameter. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4387) Issues with $it support

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4387?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4387. ----------------------------------- Resolution: Done Allowed multiple references to $it and switched the logic so that same entity detection is not needed. > Issues with $it support > ----------------------- > > Key: TEIID-4387 > URL: https://issues.jboss.org/browse/TEIID-4387 > Project: Teiid > Issue Type: Bug > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1 > > > Only a single $it reference can exist with the current logic, and it can only be used in a filter. With the refactoring to array style logic, we should be able to expand its usage. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4390) All expand level support

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4390: ------------------------------------- Summary: All expand level support Key: TEIID-4390 URL: https://issues.jboss.org/browse/TEIID-4390 Project: Teiid Issue Type: Sub-task Components: OData Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.1 We should support the level construct for expand to support recursive relationships. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4100) Full odata expand support

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4100?page=com.atlassian.jira.plugin... ] Steven Hawkins edited comment on TEIID-4100 at 8/17/16 11:23 AM: ----------------------------------------------------------------- The initial work has been completed. Follow on tasks: - support level - remove the isSameEntity logic - which is only needed for the $it construct TEIID-4387 - create an rewrite optimization to turn a single expand into a left outer join, which will preserve the performance characteristics of the old logic was (Author: shawkins): The initial work has been completed. Follow on tasks: - support level - remove the isSameEntity logic - which is only needed for the $it construct - create an rewrite optimization to turn a single expand into a left outer join, which will preserve the performance characteristics of the old logic > Full odata expand support > ------------------------- > > Key: TEIID-4100 > URL: https://issues.jboss.org/browse/TEIID-4100 > Project: Teiid > Issue Type: Feature Request > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1 > > > To move TEIID-3039 we need to have xml document model style processing for expand support. That is top down generation that supports arbitrary descendants - with targeted optimizations for projection minimization and dependent joins. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4388) If model fails to load native metadata, VDB has still status LOADING

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4388?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4388. ----------------------------------- Resolution: Rejected This is expected behavior. I'm not sure exactly what would make sense from a enhancement perspective. It would be a new timeout and would simply change the status to failed, however you can already see the reason while it's still loading with the model status. So maybe this is more of UI issue or a new state name, such as loading-retry. > If model fails to load native metadata, VDB has still status LOADING > -------------------------------------------------------------------- > > Key: TEIID-4388 > URL: https://issues.jboss.org/browse/TEIID-4388 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.12.5 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > If one model fails to load native metadata, VDB's status is still LOADING. > {code:plain|title=CLI status} > [standalone@localhost:9999 /] /subsystem=teiid:get-vdb(vdb-name=test,vdb-version=1) > { > "outcome" => "success", > "result" => { > "vdb-name" => "test", > "status" => "LOADING", > "vdb-version" => 1, > ... > "models" => [ > { > "model-name" => "Source1", > ... > "metadata-status" => "LOADED" > }, > { > "model-name" => "Source2", > ... > "validity-errors" => [ > { > "severity" => "INFO", > "message" => "TEIID50029 VDB test.1 model \"Source2\" metadata is currently being loaded. Start Time: 8/17/16 7:41 AM" > }, > { > "severity" => "ERROR", > "message" => "TEIID31178 Could not obtain connection for schema Source2, but one is required for metadata load. " > } > ], > ... > "metadata-status" => "FAILED" > }, > { > "model-name" => "Source3", > ... > "metadata-status" => "LOADED" > } > ] > } > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4388) If model fails to load native metadata, VDB has still status LOADING

by Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIID-4388?page=com.atlassian.jira.plugin... ] Juraj Duráni commented on TEIID-4388: ------------------------------------- I do not think so. 'waitForLoad' is connection URL property - it defines amount of time user is willing to wait until VDB is active. However, this should be VDB/system property. Image this scenario: # user wants to get some data from VDB, but VDB is still loading # after 10 seconds waiting for connection to VDB, application returns error message, that data is not available and suggest user to try again later. # user tries again after 5 minutes and VDB is active > If model fails to load native metadata, VDB has still status LOADING > -------------------------------------------------------------------- > > Key: TEIID-4388 > URL: https://issues.jboss.org/browse/TEIID-4388 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.12.5 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > If one model fails to load native metadata, VDB's status is still LOADING. > {code:plain|title=CLI status} > [standalone@localhost:9999 /] /subsystem=teiid:get-vdb(vdb-name=test,vdb-version=1) > { > "outcome" => "success", > "result" => { > "vdb-name" => "test", > "status" => "LOADING", > "vdb-version" => 1, > ... > "models" => [ > { > "model-name" => "Source1", > ... > "metadata-status" => "LOADED" > }, > { > "model-name" => "Source2", > ... > "validity-errors" => [ > { > "severity" => "INFO", > "message" => "TEIID50029 VDB test.1 model \"Source2\" metadata is currently being loaded. Start Time: 8/17/16 7:41 AM" > }, > { > "severity" => "ERROR", > "message" => "TEIID31178 Could not obtain connection for schema Source2, but one is required for metadata load. " > } > ], > ... > "metadata-status" => "FAILED" > }, > { > "model-name" => "Source3", > ... > "metadata-status" => "LOADED" > } > ] > } > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4388) If model fails to load native metadata, VDB has still status LOADING

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4388?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4388: ------------------------------------- Probably not, we could even take the same waitForLoad parameter into consideration for the timeout property. > If model fails to load native metadata, VDB has still status LOADING > -------------------------------------------------------------------- > > Key: TEIID-4388 > URL: https://issues.jboss.org/browse/TEIID-4388 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.12.5 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > If one model fails to load native metadata, VDB's status is still LOADING. > {code:plain|title=CLI status} > [standalone@localhost:9999 /] /subsystem=teiid:get-vdb(vdb-name=test,vdb-version=1) > { > "outcome" => "success", > "result" => { > "vdb-name" => "test", > "status" => "LOADING", > "vdb-version" => 1, > ... > "models" => [ > { > "model-name" => "Source1", > ... > "metadata-status" => "LOADED" > }, > { > "model-name" => "Source2", > ... > "validity-errors" => [ > { > "severity" => "INFO", > "message" => "TEIID50029 VDB test.1 model \"Source2\" metadata is currently being loaded. Start Time: 8/17/16 7:41 AM" > }, > { > "severity" => "ERROR", > "message" => "TEIID31178 Could not obtain connection for schema Source2, but one is required for metadata load. " > } > ], > ... > "metadata-status" => "FAILED" > }, > { > "model-name" => "Source3", > ... > "metadata-status" => "LOADED" > } > ] > } > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues August 2016