[JBoss JIRA] (TEIID-4749) Cassandra type mapping
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4749?page=com.atlassian.jira.plugin... ]
Steven Hawkins reassigned TEIID-4749:
-------------------------------------
Assignee: Steven Hawkins (was: Kylin Soong)
> Cassandra type mapping
> ----------------------
>
> Key: TEIID-4749
> URL: https://issues.jboss.org/browse/TEIID-4749
> Project: Teiid
> Issue Type: Enhancement
> Components: Misc. Connectors
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 9.3
>
>
> With TEIID-4476 there are more cassandra types mapped. When possible we should avoid mapping to Teiid object. Lists most naturally can be mapped to an array. Several of the other types may be appropriate to map this way, or even to json (for map support).
> We also need to then ensure update handling with the conversion of the runtime type back to the expected Cassandra object type.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (TEIID-4880) Join Elimination in Star Schema
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4880?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4880.
-----------------------------------
Fix Version/s: 9.3
Resolution: Done
Changed the logic to more generally run optional join removal and to look for key information with inner joins.
> Join Elimination in Star Schema
> -------------------------------
>
> Key: TEIID-4880
> URL: https://issues.jboss.org/browse/TEIID-4880
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Affects Versions: 8.7.11.6_2
> Reporter: Madou Coulibaly
> Assignee: Steven Hawkins
> Fix For: 9.3
>
>
> Suppose we have the following star schema :
> * Fact_Sales (Fact table)
> * Dim_Date, Dim_Store and Dim_Product (Dimension tables)
> Each table has a PK (id field)
> Fact_Sales has a foreign key for each dimension (date_id, store_id, product_id) in order to link them.
> Then, suppose we create an aggregate view of the fact table and its dimensions:
> SELECT
> \*
> FROM Fact_Sales F
> INNER JOIN Dim_Date D ON (F.Date_Id = D.Id)
> INNER JOIN Dim_Store S ON (F.Store_Id = S.Id)
> INNER JOIN Dim_Product P ON (F.Product_Id = P.Id)
> Suppose now we only project fields from the fact table (Fact_Sales) and just one of its dimension (Dim_Product) in a query:
> SELECT
> Fact_Sales.<fields>, Dim_Product.<fields>
> FROM aggregate_view
> During the Query Optimization, Teiid should be able to use the PK_FK constraints which link the fact table with its dimension in order to deduct that no fields from the other dimensions (Dim_Date, Dim_Store) are projected so the joins with these tables can be removed for the Query Plan.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (TEIID-4663) Support a more secure block mode for client/server encryption
by Johnathon Lee (JIRA)
[ https://issues.jboss.org/browse/TEIID-4663?page=com.atlassian.jira.plugin... ]
Johnathon Lee updated TEIID-4663:
---------------------------------
Fix Version/s: 8.12.11.6_3
> Support a more secure block mode for client/server encryption
> -------------------------------------------------------------
>
> Key: TEIID-4663
> URL: https://issues.jboss.org/browse/TEIID-4663
> Project: Teiid
> Issue Type: Quality Risk
> Components: JDBC Driver, Server
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 9.0.6, 9.1.2, 9.2, 8.12.11.6_3
>
>
> ECB is the current default for the socket transport encryption of secure messages. While this is relatively ok for small messages as we also have a message key acting as a CTR counter to some of the blocks, it does not provide strong security - especially for large data volume scenarios, such as when using larger login payloads or the secure requests option. We should default instead to CBC with an explicit initialization vector.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months