[JBoss JIRA] (TEIID-2687) Expose Translator override property definitions through Admin API
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIID-2687?page=com.atlassian.jira.plugin... ]
Barry LaFond edited comment on TEIID-2687 at 10/4/13 4:04 PM:
--------------------------------------------------------------
1) Our translator override properties that you say are for resource-adapters, are being returned on the following call:
*Admin.getTemplatePropertyDefinitions(translator.getName())*
... so we assumed that this method is actually returning property definitions for the Translator with the given name.
Lastly, the Teiid/product documentation defines a CDK (aka Connector) which defines the concept of a Connector which includes both a Translator and a Resource Adapter definition. (See Figure 1.1. JBoss Data Virtualization Architectural Overview)
was (Author: blafond):
1) Our translator override properties that you say are for resource-adapters, are being returned on the following call:
*Admin.getTemplatePropertyDefinitions(translator.getName())*
... so we assumed that this method is actually returning property definitions for the Translator with the given name.
> Expose Translator override property definitions through Admin API
> -----------------------------------------------------------------
>
> Key: TEIID-2687
> URL: https://issues.jboss.org/browse/TEIID-2687
> Project: Teiid
> Issue Type: Enhancement
> Components: AdminApi
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
>
> Currently in the admin api
> {code}
> public Collection<PropertyDefinition> getTemplatePropertyDefinitions(String templateName) throws AdminException;
> {code}
> only works with resource-adapters and data sources in terms of returning the properties that can be configured on them.
> This request is to extend the functionality to return the "overridable" properties for "translators", such as
> {code}
> public Collection<PropertyDefinition> getTemplatePropertyDefinitions(String templateName, boolean isTranslator) throws AdminException;
> {code}
--
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, 2 months
[JBoss JIRA] (TEIID-2687) Expose Translator override property definitions through Admin API
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIID-2687?page=com.atlassian.jira.plugin... ]
Barry LaFond commented on TEIID-2687:
-------------------------------------
1) Our translator override properties that you say are for resource-adapters, are being returned on the following call:
*Admin.getTemplatePropertyDefinitions(translator.getName())*
... so we assumed that this method is actually returning property definitions for the Translator with the given name.
> Expose Translator override property definitions through Admin API
> -----------------------------------------------------------------
>
> Key: TEIID-2687
> URL: https://issues.jboss.org/browse/TEIID-2687
> Project: Teiid
> Issue Type: Enhancement
> Components: AdminApi
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
>
> Currently in the admin api
> {code}
> public Collection<PropertyDefinition> getTemplatePropertyDefinitions(String templateName) throws AdminException;
> {code}
> only works with resource-adapters and data sources in terms of returning the properties that can be configured on them.
> This request is to extend the functionality to return the "overridable" properties for "translators", such as
> {code}
> public Collection<PropertyDefinition> getTemplatePropertyDefinitions(String templateName, boolean isTranslator) throws AdminException;
> {code}
--
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, 2 months
[JBoss JIRA] (TEIID-2665) Hive translator pushdown improvements
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2665?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-2665.
---------------------------------
Labels: Alpha2 (was: )
Resolution: Done
Added support for decimal, date and varchar types during the metadata import, added support for analytic functions and rollup functionality for pushdown
> Hive translator pushdown improvements
> -------------------------------------
>
> Key: TEIID-2665
> URL: https://issues.jboss.org/browse/TEIID-2665
> Project: Teiid
> Issue Type: Enhancement
> Components: Misc. Connectors
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Labels: Alpha2
> Fix For: 8.6
>
>
> - Hive 0.11 windowing functions: push down
> - Native Queries support
> - Test multi-source bindings with Hive Partition Tables - each binding to a discrete partition table
> - validate that off-heap buffer management can be used with very large data sets from Hadoop/Hive
--
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, 2 months
[JBoss JIRA] (TEIID-2688) NPE determining dependent join cost
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2688?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2688.
-----------------------------------
Resolution: Done
Corrected the logic that checks for the potential criteria placement by temporarily placing the criteria in the plan.
> NPE determining dependent join cost
> -----------------------------------
>
> Key: TEIID-2688
> URL: https://issues.jboss.org/browse/TEIID-2688
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.4
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.6
>
>
> Given that the initial node in the cost determination is not a select node if it is "pushed" to a point where the criteria is assumed to exist, then an NPE is thrown:
> java.lang.NullPointerException
> at org.teiid.query.optimizer.relational.rules.JoinUtil.replaceWithNullValues(JoinUtil.java:186)
> at org.teiid.query.optimizer.relational.rules.JoinUtil.isNullDependent(JoinUtil.java:141)
> at org.teiid.query.optimizer.relational.rules.JoinUtil.optimizeJoinType(JoinUtil.java:106)
> at org.teiid.query.optimizer.relational.rules.RulePushSelectCriteria.examinePath(RulePushSelectCriteria.java:356)
> at org.teiid.query.optimizer.relational.rules.NewCalculateCostUtil.determineTargets(NewCalculateCostUtil.java:1294)
> at org.teiid.query.optimizer.relational.rules.NewCalculateCostUtil.computeCostForDepJoin(NewCalculateCostUtil.java:1155)
> at org.teiid.query.optimizer.relational.rules.JoinRegion.getDepJoinCost(JoinRegion.java:373)
> at org.teiid.query.optimizer.relational.rules.JoinRegion.scoreRegion(JoinRegion.java:316)
> at org.teiid.query.optimizer.relational.rules.RulePlanJoins.findBestJoinOrder(RulePlanJoins.java:571)
> at org.teiid.query.optimizer.relational.rules.RulePlanJoins.execute(RulePlanJoins.java:173)
> at org.teiid.query.optimizer.relational.RelationalPlanner.executeRules(RelationalPlanner.java:525)
> at org.teiid.query.optimizer.relational.RelationalPlanner.optimize(RelationalPlanner.java:212)
> at org.teiid.query.optimizer.QueryOptimizer.optimizePlan(QueryOptimizer.java:195)
> This will occur if the prospective dependent join for example is above an outer join such that we need to check whether pushing the criteria would alter the meaning of the join.
--
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, 2 months
[JBoss JIRA] (TEIID-2687) Expose Translator override property definitions through Admin API
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2687?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-2687:
-------------------------------------
>1) Why would the Translator object return property definitions for a ResourceAdapter?
Where do we say that? it does *not* return properties for resource-adapter.
> If Connector == Translator + Resource Adapter,
Connector is a legacy term, we still have. If you want to compare to MM days above is true
>I would thought they'd be managed separately and NOT available via the Translator?
they are
2) Does the current Translator.getProperties() method return ALL possible properties for a Translator? or just the overridden properties?
All, but these are default instance properties.
> Expose Translator override property definitions through Admin API
> -----------------------------------------------------------------
>
> Key: TEIID-2687
> URL: https://issues.jboss.org/browse/TEIID-2687
> Project: Teiid
> Issue Type: Enhancement
> Components: AdminApi
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
>
> Currently in the admin api
> {code}
> public Collection<PropertyDefinition> getTemplatePropertyDefinitions(String templateName) throws AdminException;
> {code}
> only works with resource-adapters and data sources in terms of returning the properties that can be configured on them.
> This request is to extend the functionality to return the "overridable" properties for "translators", such as
> {code}
> public Collection<PropertyDefinition> getTemplatePropertyDefinitions(String templateName, boolean isTranslator) throws AdminException;
> {code}
--
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, 2 months
[JBoss JIRA] (TEIID-2687) Expose Translator override property definitions through Admin API
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIID-2687?page=com.atlassian.jira.plugin... ]
Barry LaFond commented on TEIID-2687:
-------------------------------------
That overloaded method will suffice.
Questions:
1) Why would the Translator object return property definitions for a ResourceAdapter? If Connector == Translator + Resource Adapter, I would thought they'd be managed separately and NOT available via the Translator?
2) Does the current Translator.getProperties() method return ALL possible properties for a Translator? or just the overridden properties?
> Expose Translator override property definitions through Admin API
> -----------------------------------------------------------------
>
> Key: TEIID-2687
> URL: https://issues.jboss.org/browse/TEIID-2687
> Project: Teiid
> Issue Type: Enhancement
> Components: AdminApi
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
>
> Currently in the admin api
> {code}
> public Collection<PropertyDefinition> getTemplatePropertyDefinitions(String templateName) throws AdminException;
> {code}
> only works with resource-adapters and data sources in terms of returning the properties that can be configured on them.
> This request is to extend the functionality to return the "overridable" properties for "translators", such as
> {code}
> public Collection<PropertyDefinition> getTemplatePropertyDefinitions(String templateName, boolean isTranslator) throws AdminException;
> {code}
--
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, 2 months
[JBoss JIRA] (TEIID-2688) NPE determining dependent join cost
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-2688?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-2688:
-------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1015653
> NPE determining dependent join cost
> -----------------------------------
>
> Key: TEIID-2688
> URL: https://issues.jboss.org/browse/TEIID-2688
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.4
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.6
>
>
> Given that the initial node in the cost determination is not a select node if it is "pushed" to a point where the criteria is assumed to exist, then an NPE is thrown:
> java.lang.NullPointerException
> at org.teiid.query.optimizer.relational.rules.JoinUtil.replaceWithNullValues(JoinUtil.java:186)
> at org.teiid.query.optimizer.relational.rules.JoinUtil.isNullDependent(JoinUtil.java:141)
> at org.teiid.query.optimizer.relational.rules.JoinUtil.optimizeJoinType(JoinUtil.java:106)
> at org.teiid.query.optimizer.relational.rules.RulePushSelectCriteria.examinePath(RulePushSelectCriteria.java:356)
> at org.teiid.query.optimizer.relational.rules.NewCalculateCostUtil.determineTargets(NewCalculateCostUtil.java:1294)
> at org.teiid.query.optimizer.relational.rules.NewCalculateCostUtil.computeCostForDepJoin(NewCalculateCostUtil.java:1155)
> at org.teiid.query.optimizer.relational.rules.JoinRegion.getDepJoinCost(JoinRegion.java:373)
> at org.teiid.query.optimizer.relational.rules.JoinRegion.scoreRegion(JoinRegion.java:316)
> at org.teiid.query.optimizer.relational.rules.RulePlanJoins.findBestJoinOrder(RulePlanJoins.java:571)
> at org.teiid.query.optimizer.relational.rules.RulePlanJoins.execute(RulePlanJoins.java:173)
> at org.teiid.query.optimizer.relational.RelationalPlanner.executeRules(RelationalPlanner.java:525)
> at org.teiid.query.optimizer.relational.RelationalPlanner.optimize(RelationalPlanner.java:212)
> at org.teiid.query.optimizer.QueryOptimizer.optimizePlan(QueryOptimizer.java:195)
> This will occur if the prospective dependent join for example is above an outer join such that we need to check whether pushing the criteria would alter the meaning of the join.
--
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, 2 months
[JBoss JIRA] (TEIID-2688) NPE determining dependent join cost
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2688:
-------------------------------------
Summary: NPE determining dependent join cost
Key: TEIID-2688
URL: https://issues.jboss.org/browse/TEIID-2688
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.4
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.6
Given that the initial node in the cost determination is not a select node if it is "pushed" to a point where the criteria is assumed to exist, then an NPE is thrown:
java.lang.NullPointerException
at org.teiid.query.optimizer.relational.rules.JoinUtil.replaceWithNullValues(JoinUtil.java:186)
at org.teiid.query.optimizer.relational.rules.JoinUtil.isNullDependent(JoinUtil.java:141)
at org.teiid.query.optimizer.relational.rules.JoinUtil.optimizeJoinType(JoinUtil.java:106)
at org.teiid.query.optimizer.relational.rules.RulePushSelectCriteria.examinePath(RulePushSelectCriteria.java:356)
at org.teiid.query.optimizer.relational.rules.NewCalculateCostUtil.determineTargets(NewCalculateCostUtil.java:1294)
at org.teiid.query.optimizer.relational.rules.NewCalculateCostUtil.computeCostForDepJoin(NewCalculateCostUtil.java:1155)
at org.teiid.query.optimizer.relational.rules.JoinRegion.getDepJoinCost(JoinRegion.java:373)
at org.teiid.query.optimizer.relational.rules.JoinRegion.scoreRegion(JoinRegion.java:316)
at org.teiid.query.optimizer.relational.rules.RulePlanJoins.findBestJoinOrder(RulePlanJoins.java:571)
at org.teiid.query.optimizer.relational.rules.RulePlanJoins.execute(RulePlanJoins.java:173)
at org.teiid.query.optimizer.relational.RelationalPlanner.executeRules(RelationalPlanner.java:525)
at org.teiid.query.optimizer.relational.RelationalPlanner.optimize(RelationalPlanner.java:212)
at org.teiid.query.optimizer.QueryOptimizer.optimizePlan(QueryOptimizer.java:195)
This will occur if the prospective dependent join for example is above an outer join such that we need to check whether pushing the criteria would alter the meaning of the join.
--
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, 2 months
[JBoss JIRA] (TEIID-2687) Expose Translator override property definitions through Admin API
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIID-2687:
-----------------------------------
Summary: Expose Translator override property definitions through Admin API
Key: TEIID-2687
URL: https://issues.jboss.org/browse/TEIID-2687
Project: Teiid
Issue Type: Enhancement
Components: AdminApi
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Currently in the admin api
{code}
public Collection<PropertyDefinition> getTemplatePropertyDefinitions(String templateName) throws AdminException;
{code}
only works with resource-adapters and data sources in terms of returning the properties that can be configured on them.
This request is to extend the functionality to return the "overridable" properties for "translators", such as
{code}
public Collection<PropertyDefinition> getTemplatePropertyDefinitions(String templateName, boolean isTranslator) throws AdminException;
{code}
--
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, 2 months