[JBoss JIRA] (TEIID-5373) Dependent set created from prepared IN predicate fails
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-5373:
-------------------------------------
Summary: Dependent set created from prepared IN predicate fails
Key: TEIID-5373
URL: https://issues.jboss.org/browse/TEIID-5373
Project: Teiid
Issue Type: Bug
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 11.0, 10.3.2
If an IN predicate is used as a dependent set - for example when used as a procedural relational parameter or when it's too large and must be split among source commands - the dependentcriteriaprocessor will throw an assertionerror with "unknown predicate type"
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months
[JBoss JIRA] (TEIID-5235) Could not find symbol in processing an inline view using except
by Jan Stastny (JIRA)
[ https://issues.jboss.org/browse/TEIID-5235?page=com.atlassian.jira.plugin... ]
Jan Stastny commented on TEIID-5235:
------------------------------------
Only small note for future reference.
The issue could be also observed with intersect, not only except.
> Could not find symbol in processing an inline view using except
> ---------------------------------------------------------------
>
> Key: TEIID-5235
> URL: https://issues.jboss.org/browse/TEIID-5235
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 10.1, 10.0.3, 8.12.14.6_4
>
>
> With a query such as:
> SELECT case when agent_tin_id is null then 'Y' else 'N' end agent_tin_id from (SELECT agent_tin_id from MySQL_Server.bitool.AGENT_DIM where agent_tin_id>100 except( SELECT agent_tin_id from MySQL_Server.bitool.AGENT_DIM where agent_tin_id=100)) a
> When not fully pushed is processed as an anti semi join, but results in an exception:
> {code}
> org.teiid.core.TeiidRuntimeException: Planning error. Could not find symbol: a.agent_tin_id
> at org.teiid.query.processor.relational.RelationalNode.getProjectionIndexes(RelationalNode.java:363)
> at org.teiid.query.processor.relational.JoinNode.initialize(JoinNode.java:129)
> at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:92)
> at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:98)
> at org.teiid.query.processor.relational.RelationalPlan.initialize(RelationalPlan.java:87)
> at org.teiid.query.processor.QueryProcessor.init(QueryProcessor.java:223)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months
[JBoss JIRA] (TEIID-5372) Enhance docker support
by Rafal Korytkowski (JIRA)
[ https://issues.jboss.org/browse/TEIID-5372?page=com.atlassian.jira.plugin... ]
Work on TEIID-5372 started by Rafal Korytkowski.
------------------------------------------------
> Enhance docker support
> ----------------------
>
> Key: TEIID-5372
> URL: https://issues.jboss.org/browse/TEIID-5372
> Project: Teiid
> Issue Type: Enhancement
> Reporter: Rafal Korytkowski
> Assignee: Rafal Korytkowski
> Priority: Optional
>
> Currently there's limited support for docker in Teiid, which can be enabled by adding -Ddocker=true to the build command. The generated image is based on CentOS and running standalone on the Wildfly server. Latest builds are pushed to https://hub.docker.com/r/jboss/teiid/, but versions are not tagged automatically with releases. Development with Docker is not supported.
> Proposed changes:
> 1. Produce docker image based on Alpine, which is better suited for microservices, in addition to CentOS.
> 2. Automatically tag versions in Docker when doing releases.
> 3. Support development by providing a docker-compose file with the possibility to start server in a debug mode and enabled auto-redeployment of code changes.
> 4. Optionally provide a Docker image for building code using maven in Docker. Having Docker as the only prerequisite is convenient for CI environments and makes the build environment agnostic.
> [~shawkins], [~rareddy], thoughts?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months
[JBoss JIRA] (TEIID-5372) Enhance docker support
by Rafal Korytkowski (JIRA)
Rafal Korytkowski created TEIID-5372:
----------------------------------------
Summary: Enhance docker support
Key: TEIID-5372
URL: https://issues.jboss.org/browse/TEIID-5372
Project: Teiid
Issue Type: Enhancement
Reporter: Rafal Korytkowski
Assignee: Steven Hawkins
Priority: Optional
Currently there's limited support for docker in Teiid, which can be enabled by adding -Ddocker=true to the build command. The generated image is based on CentOS and running standalone on the Wildfly server. Latest builds are pushed to https://hub.docker.com/r/jboss/teiid/, but versions are not tagged automatically with releases. Development with Docker is not supported.
Proposed changes:
1. Produce docker image based on Alpine, which is better suited for microservices, in addition to CentOS.
2. Automatically tag versions in Docker when doing releases.
3. Support development by providing a docker-compose file with the possibility to start server in a debug mode and enabled auto-redeployment of code changes.
4. Optionally provide a Docker image for building code using maven in Docker. Having Docker as the only prerequisite is convenient for CI environments and makes the build environment agnostic.
[~shawkins], [~rareddy], thoughts?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months
[JBoss JIRA] (TEIID-5285) Add high-level feature for redirection of updates
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-5285?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-5285:
-------------------------------------
[~shawkins] Ignore above, that was my mistake in table creation.
> Add high-level feature for redirection of updates
> -------------------------------------------------
>
> Key: TEIID-5285
> URL: https://issues.jboss.org/browse/TEIID-5285
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine, Teiid Spring Boot
> Reporter: Steven Hawkins
> Assignee: Ramesh Reddy
> Fix For: 11.x
>
>
> In microservices testing it is desirable to test against production/live data but not commit any updates. We should offer a simple solution that can defined by extension metadata and enabled/disabled by a feature flag. We may need to make simplifying assumptions about the scope (per session, per application, etc.) and durability of the updates.
> Under the covers this will be achieved by using views, update triggers, and a store for the updates and when not enabled the expectation is that all operations should pass through. However the application will be limited to using Teiid SQL and will be required to use the Teiid or pg driver, or Teiid spring boot.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months
[JBoss JIRA] (TEIID-5285) Add high-level feature for redirection of updates
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-5285?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-5285:
-------------------------------------
[~shawkins] I started with
{code}
<vdb name="redirection" version="1">
<!--1-insert, 2-update, 3-delete for status-->
<model visible="false" name="master">
<source name="master" translator-name="postgresql" connection-jndi-name="java:/pgMaster"/>
<metadata type = "DDL"><![CDATA[
CREATE FOREIGN TABLE CUSTOMER
(
SSN varchar(10),
FIRSTNAME varchar(64),
LASTNAME varchar(64),
ST_ADDRESS varchar(256),
APT_NUMBER varchar(32),
CITY varchar(64),
STATE varchar(32),
ZIPCODE varchar(10),
PHONE varchar(15),
PRIMARY KEY(SSN)
) OPTIONS (UPDATABLE 'FALSE');
CREATE FOREIGN TABLE CUSTOMER_MODIFIED
(
SSN varchar(10),
FIRSTNAME varchar(64),
LASTNAME varchar(64),
ST_ADDRESS varchar(256),
APT_NUMBER varchar(32),
CITY varchar(64),
STATE varchar(32),
ZIPCODE varchar(10),
PHONE varchar(15),
STATUS integer,
PRIMARY KEY(SSN)
) OPTIONS (UPDATABLE 'TRUE');
]]>
</metadata>
</model>
<model name="whatever" type="VIRTUAL">
<metadata type = "DDL"><![CDATA[
CREATE VIEW customer OPTIONS (UPDATABLE 'TRUE') AS
SELECT o.SSN, o.FIRSTNAME, o.LASTNAME, o.PHONE FROM master.CUSTOMER o LEFT OUTER JOIN master.CUSTOMER_MODIFIED m ON (o.SSN=m.SSN) where m.STATUS is null
UNION ALL
SELECT SSN, FIRSTNAME, LASTNAME, PHONE FROM master.CUSTOMER_MODIFIED where STATUS <> 3;
CREATE TRIGGER ON customer INSTEAD OF INSERT AS
FOR EACH ROW
BEGIN ATOMIC
UPSERT INTO master.CUSTOMER_MODIFIED (SSN, FIRSTNAME, LASTNAME, PHONE, STATUS) values (NEW.SSN, NEW.FIRSTNAME, NEW.LASTNAME, NEW.PHONE, 1);
END;
CREATE TRIGGER ON customer INSTEAD OF DELETE AS
FOR EACH ROW
BEGIN ATOMIC
UPSERT INTO master.CUSTOMER_MODIFIED (SSN, FIRSTNAME, LASTNAME, PHONE, STATUS) values (OLD.SSN, OLD.FIRSTNAME, OLD.LASTNAME, OLD.PHONE, 3);
END;
CREATE TRIGGER ON customer INSTEAD OF UPDATE AS
FOR EACH ROW
BEGIN ATOMIC
IF (CHANGING.SSN)
BEGIN
DECLARE string VARIABLES.X = (SELECT SSN FROM master.CUSTOMER_MODIFIED);
IF (VARIABLES.X is NULL)
BEGIN
UPSERT INTO master.CUSTOMER_MODIFIED (SSN, STATUS) values (OLD.SSN, 3);
UPSERT INTO master.CUSTOMER_MODIFIED (SSN, FIRSTNAME, LASTNAME, PHONE, STATUS) values (NEW.SSN, NEW.FIRSTNAME, NEW.LASTNAME, NEW.PHONE, 1);
END ELSE
BEGIN
RAISE SQLEXCEPTION 'duplicate key';
END
END ELSE
BEGIN
UPSERT INTO master.CUSTOMER_MODIFIED (SSN, FIRSTNAME, LASTNAME, PHONE, STATUS) values (NEW.SSN, NEW.FIRSTNAME, NEW.LASTNAME, NEW.PHONE, 2);
END
END;
]]>
</metadata>
</model>
</vdb>
{code}
and executed
{code}
delete from customer where SSN = 'CST01006'
insert into customer (SSN, FIRSTNAME, LASTNAME, PHONE) values ('1111', 'Ramesh', 'Reddy', '(314)-555-1212');
update customer set FIRSTNAME = 'Bob' where SSN = 'CST01035';
update customer set FIRSTNAME = 'Henry' where SSN = 'CST01035';
{code}
When it came to second update it was not taking place. Not sure, what needs to be changed?
> Add high-level feature for redirection of updates
> -------------------------------------------------
>
> Key: TEIID-5285
> URL: https://issues.jboss.org/browse/TEIID-5285
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine, Teiid Spring Boot
> Reporter: Steven Hawkins
> Assignee: Ramesh Reddy
> Fix For: 11.x
>
>
> In microservices testing it is desirable to test against production/live data but not commit any updates. We should offer a simple solution that can defined by extension metadata and enabled/disabled by a feature flag. We may need to make simplifying assumptions about the scope (per session, per application, etc.) and durability of the updates.
> Under the covers this will be achieved by using views, update triggers, and a store for the updates and when not enabled the expectation is that all operations should pass through. However the application will be limited to using Teiid SQL and will be required to use the Teiid or pg driver, or Teiid spring boot.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months
[JBoss JIRA] (TEIID-3075) OSGi bundle versions hardcoded
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3075?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3075.
-----------------------------------
Fix Version/s: (was: 11.x)
Resolution: Won't Fix
Marking as won't fix. There's no plans on the horizon to work as an OSGi bundle.
> OSGi bundle versions hardcoded
> ------------------------------
>
> Key: TEIID-3075
> URL: https://issues.jboss.org/browse/TEIID-3075
> Project: Teiid
> Issue Type: Bug
> Components: Build/Kits
> Affects Versions: 8.7.1
> Reporter: Julian Coleman
> Priority: Minor
>
> The file:
> build/kits/karaf/teiid-karaf-features.xml
> contains hard-coded versions of some dependencies. For example:
> <bundle>wrap:mvn:org.apache.lucene/lucene-core/3.6.2</bundle>
> <bundle>mvn:org.infinispan/infinispan-query/5.2.1.Final</bundle>
> These should be replaced by the appropriate properties.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months