[JBoss JIRA] (TEIID-3928) Usage with analytical platforms
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3928?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3928:
----------------------------------
Fix Version/s: 10.x
> Usage with analytical platforms
> -------------------------------
>
> Key: TEIID-3928
> URL: https://issues.jboss.org/browse/TEIID-3928
> Project: Teiid
> Issue Type: Sub-task
> Affects Versions: 9.x
> Reporter: Kylin Soong
> Assignee: Kylin Soong
> Fix For: 9.x, 10.x
>
>
> We should promote analytical platforms, such as Spark/Hive/PrestoDB, with usages of Teiid/DV as a data loader (we support a wider variety of sources can have views that perform incoming transformation/filtering logic) and for top level integration (since we provide more robust client support, transaction support, and broader federation). This effort will include documentation, additional integration code, and sample code.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (TEIID-587) Better pushdown support for exotic joins
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-587?page=com.atlassian.jira.plugin.... ]
Steven Hawkins updated TEIID-587:
---------------------------------
Fix Version/s: 10.x
> Better pushdown support for exotic joins
> ----------------------------------------
>
> Key: TEIID-587
> URL: https://issues.jboss.org/browse/TEIID-587
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Affects Versions: 6.1.0
> Reporter: Steven Hawkins
> Fix For: 9.x, 10.x
>
>
> Our optimizations get in the way of Salesforce pushdown. Specifically rewriting like when possible to = and converting outer joins to inner joins. In both cases we would need to not perform the optimization in the first place or convert into an acceptable form prior to pushdown.
> The next is that salesforce, while requiring key criteria also allows other criteria in the left outer join on clause (which would be the same as having criteria on the nested relationship query in the salesforce query). With the capabilities as currently defined this would cause the query to not be pushed down. We should consider adding a relational supported join criteria type that requires key criteria but allows for outside criteria. Also we should treat the lack of inner join support to mean that criteria on the inner side of an outer join cannot be pushed.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (TEIID-4315) HBase Quickstart issues
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4315?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-4315:
----------------------------------
Fix Version/s: 9.3
(was: 9.x)
Need to evaluate if these for 9.3 or push to 10.x
> HBase Quickstart issues
> -----------------------
>
> Key: TEIID-4315
> URL: https://issues.jboss.org/browse/TEIID-4315
> Project: Teiid
> Issue Type: Bug
> Components: Quick Starts
> Affects Versions: 9.x
> Reporter: Van Halbert
> Assignee: Van Halbert
> Priority: Minor
> Fix For: 9.3
>
>
> remove.cli script does not work. You need to remove items in revers order. You cannot remove driver if some data source is still using it. Please update remove.cli script:
> From:
> > module remove --name=org.apache.phoenix
> > /subsystem=datasources/jdbc-driver=phoenix:remove()
> > /subsystem=datasources/data-source=QSPhoenixDS:remove()
> To:
> > /subsystem=datasources/data-source=QSPhoenixDS:remove()
> > /subsystem=datasources/jdbc-driver=phoenix:remove()
> > module remove --name=org.apache.phoenix
> -------
> As far as I know, option 'enabled=true' of 'add' operation for data-source is deprecated in CLI. Moreover, user needs to reload server to be able to use create data source. Please, update the script like follows:
> From:
> > /subsystem=datasources/data-source=QSPhoenixDS:add(jndi-name="java:/QSPhoenixDS",driver-name=phoenix,connection-url=jdbc:phoenix:127.0.0.1:2181,user-name=sa,password=sa,enabled=true,use-java-context=true)
> To:
> > /subsystem=datasources/data-source=QSPhoenixDS:add(jndi-name="java:/QSPhoenixDS",driver-name=phoenix,connection-url=jdbc:phoenix:127.0.0.1:2181,user-name=sa,password=sa,use-java-context=true)
> > /subsystem=datasources/data-source=QSPhoenixDS:enable
> ------
> Files: hbase-as-a-datasource/README.md, hbase-as-a-datasource/src/scripts/setup.cli
> Line: 57 - 3) Setup Phoenix Data Source
> 1 - --resources=phoenix-4.2.1-client.jar
> Please add an instruction to update phoenix version in setup.cli script if user uses different version of phoenix/hbase.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months