March 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2909) Provide more info for TeiidPropertyDefinition marked 'isRequired' but with conditions

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIID-2909?page=com.atlassian.jira.plugin... ] Barry LaFond commented on TEIID-2909: ------------------------------------- We're not asking for a conversational API. We are asking for a more complex translator property definition that can some how be used in Teiid Designer without having to add custom business logic. I'm assuming that you've got these additional property dependencies/conditions coded in the translator's validation or translator usage logic. If the condition is "passive" (where "required" properties are not conditional on other non-required properties) then we wouldn't need to provide that validation. But in this case, users would see *property_1* as required and not know that it's not required because *property_2* was set to *false*. Without that validation on our side, users will set *property_1*, then deploy/execute/test their VDB and it just wouldn't work and maybe they'd get a server log warning/error that *property_2* is not *true* > Provide more info for TeiidPropertyDefinition marked 'isRequired' but with conditions > ------------------------------------------------------------------------------------- > > Key: TEIID-2909 > URL: https://issues.jboss.org/browse/TEIID-2909 > Project: Teiid > Issue Type: Feature Request > Components: AdminApi > Affects Versions: 8.4 > Reporter: Mark Drilling > Assignee: Steven Hawkins > > For some data source types, there are associated propertyDefinitions that are marked 'required'. However, they are not always required. > I'm referring to TeiidPropertyDefinition list returned by adminApi.getTemplatePropertyDefns(), for example. > Google source is example of a source containing this type of property definition. > https://docs.jboss.org/author/display/teiid84final/Google+Spreadsheet+Dat... > For example 'RefreshToken' is marked as required, but it is only required based on the value of another property (AuthMethod). > Can teiid provide these additional conditions along with the propertyDefinition? Without this information we are forced to hard-code the validation rules into our client application. -- 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

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2909) Provide more info for TeiidPropertyDefinition marked 'isRequired' but with conditions

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2909?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2909: ------------------------------------- There is no conversational state in this API, so it is not possible. If that is case then the property needs to split up or named differently to infer the meaning. As Designer needs to be concerned it just need to enforce "isrequired" or not > Provide more info for TeiidPropertyDefinition marked 'isRequired' but with conditions > ------------------------------------------------------------------------------------- > > Key: TEIID-2909 > URL: https://issues.jboss.org/browse/TEIID-2909 > Project: Teiid > Issue Type: Feature Request > Components: AdminApi > Affects Versions: 8.4 > Reporter: Mark Drilling > Assignee: Steven Hawkins > > For some data source types, there are associated propertyDefinitions that are marked 'required'. However, they are not always required. > I'm referring to TeiidPropertyDefinition list returned by adminApi.getTemplatePropertyDefns(), for example. > Google source is example of a source containing this type of property definition. > https://docs.jboss.org/author/display/teiid84final/Google+Spreadsheet+Dat... > For example 'RefreshToken' is marked as required, but it is only required based on the value of another property (AuthMethod). > Can teiid provide these additional conditions along with the propertyDefinition? Without this information we are forced to hard-code the validation rules into our client application. -- 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

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2909) Provide more info for TeiidPropertyDefinition marked 'isRequired' but with conditions

by Mark Drilling (JIRA)

Mark Drilling created TEIID-2909: ------------------------------------ Summary: Provide more info for TeiidPropertyDefinition marked 'isRequired' but with conditions Key: TEIID-2909 URL: https://issues.jboss.org/browse/TEIID-2909 Project: Teiid Issue Type: Feature Request Components: AdminApi Affects Versions: 8.4 Reporter: Mark Drilling Assignee: Steven Hawkins For some data source types, there are associated propertyDefinitions that are marked 'required'. However, they are not always required. I'm referring to TeiidPropertyDefinition list returned by adminApi.getTemplatePropertyDefns(), for example. Google source is example of a source containing this type of property definition. https://docs.jboss.org/author/display/teiid84final/Google+Spreadsheet+Dat... For example 'RefreshToken' is marked as required, but it is only required based on the value of another property (AuthMethod). Can teiid provide these additional conditions along with the propertyDefinition? Without this information we are forced to hard-code the validation rules into our client application. -- 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

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2818) Use Oauth SAML Grant Type

by Anil Saldhana (JIRA)

[ https://issues.jboss.org/browse/TEIID-2818?page=com.atlassian.jira.plugin... ] Anil Saldhana commented on TEIID-2818: -------------------------------------- New location for PicketLink OAuth dashboard: http://picketlink.org/federation/oauth/oauth/ > Use Oauth SAML Grant Type > ------------------------- > > Key: TEIID-2818 > URL: https://issues.jboss.org/browse/TEIID-2818 > Project: Teiid > Issue Type: Feature Request > Components: Server > Reporter: Van Halbert > Assignee: Ramesh Reddy > Fix For: 8.7.1 > > > How to connect to underlying data sources on behalf of Oauth when user comes into webservice with Oauth? > Use cases: > 1 – client u/p sources: oauth/saml > 2- client : oauth/saml sorces u/p, other > 3 – client: Oauth/saml sources Oauth/saml (data sources are also secured by Oauth) – > 3a) propogate sources and 3b – resolve new tokens for sources > Link: http://www.layer7tech.com/tutorials/oauth-20-with-layer-7-gateways-tutori... -- 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

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2885) Allow dependent join pushdown to be chosen by the planner

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2885?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2885: ---------------------------------- Fix Version/s: 8.7.1 (was: 8.7) > Allow dependent join pushdown to be chosen by the planner > --------------------------------------------------------- > > Key: TEIID-2885 > URL: https://issues.jboss.org/browse/TEIID-2885 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.1 > > > As a follow on to TEIID-2249, the planner should be able to choose when to use full join pushdown, rather than only relying upon a hint. One downside to this currently is that there isn't a good way to do a back off to a different join processing (unless we embedded an alternative plan) and so we may have to add failure logic if too many independent values are retrieved. -- 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

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-1226) Reuse dynamic sql plans and allow for prepared statements in procedure logic

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1226?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-1226: ---------------------------------- Fix Version/s: 9.x (was: 8.7) Bumping further out as there hasn't been a direct need yet and progress has been slow. > Reuse dynamic sql plans and allow for prepared statements in procedure logic > ---------------------------------------------------------------------------- > > Key: TEIID-1226 > URL: https://issues.jboss.org/browse/TEIID-1226 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 7.1 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 9.x > > > Dynamic sql plans (for dynamic sql statements, lookup, and matview refreshes) should allow for plan reuse. > Also procedure logic should have a mechanism to execute prepared statements for further plan reuse. -- 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

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-1226) Reuse dynamic sql plans and allow for prepared statements in procedure logic

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1226?page=com.atlassian.jira.plugin... ] Work on TEIID-1226 stopped by Steven Hawkins. > Reuse dynamic sql plans and allow for prepared statements in procedure logic > ---------------------------------------------------------------------------- > > Key: TEIID-1226 > URL: https://issues.jboss.org/browse/TEIID-1226 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 7.1 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 8.7 > > > Dynamic sql plans (for dynamic sql statements, lookup, and matview refreshes) should allow for plan reuse. > Also procedure logic should have a mechanism to execute prepared statements for further plan reuse. -- 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

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2908) Increase default number of socket workers

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2908?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2908. ----------------------------------- Resolution: Done changed the default to 2*the available processors (matches netty) or 4 which ever is larger. > Increase default number of socket workers > ----------------------------------------- > > Key: TEIID-2908 > URL: https://issues.jboss.org/browse/TEIID-2908 > Project: Teiid > Issue Type: Quality Risk > Components: Server > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7 > > > With recent performance testing it was noticed under load that having a constrained number of socket workers slows down the creation of new connections when the server is heavily loaded (meaning that the socket workers are largely dedicated to queued data i/o work). -- 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

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2908) Increase default number of socket workers

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2908: ------------------------------------- Summary: Increase default number of socket workers Key: TEIID-2908 URL: https://issues.jboss.org/browse/TEIID-2908 Project: Teiid Issue Type: Quality Risk Components: Server Affects Versions: 7.7 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.7 With recent performance testing it was noticed under load that having a constrained number of socket workers slows down the creation of new connections when the server is heavily loaded (meaning that the socket workers are largely dedicated to queued data i/o work). -- 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

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2907) Uncaught exception during rollback

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2907?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2907. ----------------------------------- Resolution: Done Changed the code to convert the illegalstateexception into a checked exception. > Uncaught exception during rollback > ---------------------------------- > > Key: TEIID-2907 > URL: https://issues.jboss.org/browse/TEIID-2907 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7 > > > TransactionManager.rollback can throw an illegalstateexception, which if uncaught can mask other issues. -- 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

10 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2014