[JBoss JIRA] (TEIID-4719) Add a ddl equivalent to the metadata tag
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-4719:
-------------------------------------
Summary: Add a ddl equivalent to the metadata tag
Key: TEIID-4719
URL: https://issues.jboss.org/browse/TEIID-4719
Project: Teiid
Issue Type: Sub-task
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Generally we'll need something that is equivalent to the metadata tag - that can specify a repo and options. In a zip deployment this will allow splitting the ddl over multiple files.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (TEIID-4717) Add Support for 'ALLOW FILTERING' in Teiid Cassandra Translator
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4717?page=com.atlassian.jira.plugin... ]
Steven Hawkins reassigned TEIID-4717:
-------------------------------------
Issue Type: Enhancement (was: Feature Request)
Component/s: Misc. Connectors
Fix Version/s: 9.3
Assignee: (was: Steven Hawkins)
Would you expect that the translator to infer this hint automatically from the index metadata on the source table, or would this be driven by a source hint provided in the user query?
> Add Support for 'ALLOW FILTERING' in Teiid Cassandra Translator
> ---------------------------------------------------------------
>
> Key: TEIID-4717
> URL: https://issues.jboss.org/browse/TEIID-4717
> Project: Teiid
> Issue Type: Enhancement
> Components: Misc. Connectors
> Reporter: Vijay K
> Labels: cassandra
> Fix For: 9.3
>
>
> At certain times it is unavoidable to use few columns in the where clause which are not part of the index, in that case Cassandra driver throws error
> {color:red}Bad Request: Cannot execute this query as it might involve data filtering and thus may have unpredictable performance. If you want to execute this query despite the performance unpredictability, use ALLOW FILTERING{color}
> As as user I should be able to configure the Cassandra translator to append *ALLOW FILTERING* to the generated query (CQL)
> References:
> https://www.datastax.com/dev/blog/allow-filtering-explained-2
> https://developer.jboss.org/thread/239011
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (TEIID-3624) No way to associate enterprise data types in dynamic vdb constructs
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3624?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3624:
---------------------------------------
We'll add support for create domain with the standard type options that we support. With the new ddl support, we'll be able to support these statements at a vdb level - which is the same support as the old enterprise data types. Otherwise creating them under a schema would imply schema scoping, which would require new support.
> No way to associate enterprise data types in dynamic vdb constructs
> -------------------------------------------------------------------
>
> Key: TEIID-3624
> URL: https://issues.jboss.org/browse/TEIID-3624
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Fix For: 9.2
>
>
> I don't find any doc's on how to define enterprise data types in a dynamic vdb.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (TEIID-4627) High-level event handling
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4627?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4627:
---------------------------------------
Yes sorry I overlooked that.
> High-level event handling
> -------------------------
>
> Key: TEIID-4627
> URL: https://issues.jboss.org/browse/TEIID-4627
> Project: Teiid
> Issue Type: Enhancement
> Components: Grammar, Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 9.2
>
>
> We should look into high-level plugability of event handling at a row level. This could even be handled at the language level with new trigger semantics for source tables: create trigger on tbl on cdc (insert|update...) - which could potentially even specify the topic mapping other details. There is complexity for multi-source models here though.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (TEIID-4629) Offer a ddl solution to replace the vdb.xml
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4629?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4629:
---------------------------------------
> Can you elaborate on concepts removed
A lot of the changes were just to bring things in line with master, which could have been just formatting. Other changes were to pull out any of the client changes, embedded connection reconnect logic, and authorization.
> Let's handle this as separate JIRA.
I'm fine with that. Generally we'll need something that is equivalent to the metadata tag - that can specify a repo and options.
Another small consideration is that source loading based upon ddl is serialized. We may need to have access to native metadata spawn a job.
> Offer a ddl solution to replace the vdb.xml
> -------------------------------------------
>
> Key: TEIID-4629
> URL: https://issues.jboss.org/browse/TEIID-4629
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine, Server
> Reporter: Steven Hawkins
> Assignee: Ramesh Reddy
> Fix For: 9.2
>
>
> Based upon the work on TEIID-2578 we should first offer the ability to replace the vdb.xml with ddl. We can additionally include some of the work to represent additional pieces of the vdb as api level metadata objects (instead of in the admin layer) where possible. Ideally this should support as much alter functionality as possible.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (TEIID-4629) Offer a ddl solution to replace the vdb.xml
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4629?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-4629:
-------------------------------------
Thank you [~shawkins], I know this was huge review to go through. Can you elaborate on concepts removed, I tried to diff the commit, but no luck there.
Yes, for the ZIP archive we need a extension to IMPORT statement or something like INCLUDE. I would think it would be good to have explicit notion of how these external DDL files are included compare to some pseudo name/order way to include them. Let's handle this as separate JIRA.
> Offer a ddl solution to replace the vdb.xml
> -------------------------------------------
>
> Key: TEIID-4629
> URL: https://issues.jboss.org/browse/TEIID-4629
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine, Server
> Reporter: Steven Hawkins
> Assignee: Ramesh Reddy
> Fix For: 9.2
>
>
> Based upon the work on TEIID-2578 we should first offer the ability to replace the vdb.xml with ddl. We can additionally include some of the work to represent additional pieces of the vdb as api level metadata objects (instead of in the admin layer) where possible. Ideally this should support as much alter functionality as possible.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (TEIID-4627) High-level event handling
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4627?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-4627:
-------------------------------------
I can't seem to duplicate with Embedded engine, but I think the issue is "SourceTriggerActionPlanner.CompositeProcessorPlan.nextPlan()" returns a TupleBatch without a termination flag.
> High-level event handling
> -------------------------
>
> Key: TEIID-4627
> URL: https://issues.jboss.org/browse/TEIID-4627
> Project: Teiid
> Issue Type: Enhancement
> Components: Grammar, Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 9.2
>
>
> We should look into high-level plugability of event handling at a row level. This could even be handled at the language level with new trigger semantics for source tables: create trigger on tbl on cdc (insert|update...) - which could potentially even specify the topic mapping other details. There is complexity for multi-source models here though.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months