August 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4155) Explore the possibility to use JBeret as materialization schedular

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4155?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-4155: ------------------------------------ The fact that JBeret is a batching (reading/writing) project, it could be beneficial to utilize their batching abilities, especially for large volumes. > Explore the possibility to use JBeret as materialization schedular > ------------------------------------------------------------------ > > Key: TEIID-4155 > URL: https://issues.jboss.org/browse/TEIID-4155 > Project: Teiid > Issue Type: Sub-task > Components: Server > Reporter: Ramesh Reddy > > Right now the managed external materialization uses the our own very basic job scheduler, it would be nice if we can use JBeret batch processing system to automatically create jobs based on the materialization extension properties. > JBeret is JSR-352, looks simple enough to integrate. The advantages for us would be > - a standard scheduler, which will also work in "embedded" as this supposed to work in Java SE > - Gives CLI based management > - may be better metrics on time taken and error management -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4155) Explore the possibility to use JBeret as materialization schedular

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4155?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-4155: ------------------------------------ JBeret does have some example applications: https://github.com/jberet/jsr352/tree/master/wildfly-jberet-samples/sched... https://github.com/jberet/jsr352/tree/master/wildfly-jberet-samples/sched... > Explore the possibility to use JBeret as materialization schedular > ------------------------------------------------------------------ > > Key: TEIID-4155 > URL: https://issues.jboss.org/browse/TEIID-4155 > Project: Teiid > Issue Type: Sub-task > Components: Server > Reporter: Ramesh Reddy > > Right now the managed external materialization uses the our own very basic job scheduler, it would be nice if we can use JBeret batch processing system to automatically create jobs based on the materialization extension properties. > JBeret is JSR-352, looks simple enough to integrate. The advantages for us would be > - a standard scheduler, which will also work in "embedded" as this supposed to work in Java SE > - Gives CLI based management > - may be better metrics on time taken and error management -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4368) Fail to deploy VDB with TextTable SELECTOR, ROW DELIMITER, HEADER

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4368?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4368: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1362031|https://bugzilla.redhat.com/show_bug.cgi?id=1362031] from NEW to CLOSED > Fail to deploy VDB with TextTable SELECTOR, ROW DELIMITER, HEADER > ----------------------------------------------------------------- > > Key: TEIID-4368 > URL: https://issues.jboss.org/browse/TEIID-4368 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7 > Reporter: Lucie Fabrikova > Assignee: Steven Hawkins > Attachments: texttabvdb-vdb.xml > > > Server fails to deploy dynamic vdb with models which contain following TextTable parameters: SELECTOR, ROW DELIMITER, HEADER. > Part of server log: > 10:24:02,171 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "texttabvdb-vdb.xml" (runtime-name: "texttabvdb-vdb.xml") > 10:24:02,213 INFO [org.teiid.RUNTIME] (MSC service thread 1-6) TEIID50029 VDB texttab.1 model "model2" metadata is currently being loaded. Start Time: 8/1/16 10:24 AM > 10:24:02,214 INFO [org.teiid.RUNTIME] (MSC service thread 1-6) TEIID50029 VDB texttab.1 model "model3" metadata is currently being loaded. Start Time: 8/1/16 10:24 AM > 10:24:02,217 WARN [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID50036 VDB texttab.1 model "model2" metadata failed to load. Reason:TEIID30386 org.teiid.api.exception.query.QueryParserException: TEIID31100 Parsing error: Encountered "COLUMNS col1 string [*]ROW[*] DELIMITER 'X'" at line 7, column 59. > Was expecting: "escape" | "no" | "selector" | "skip" | "width" | "delimiter" | "quote" | "header" | "," | "(" ... > 10:24:02,218 WARN [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID50036 VDB texttab.1 model "model3" metadata failed to load. Reason:TEIID30386 org.teiid.api.exception.query.QueryParserException: TEIID31100 Parsing error: Encountered ") COLUMNS a [*]HEADER[*] 'a' string" at line 7, column 52. > Was expecting: "string" | "varbinary" | "varchar" | "boolean" | "byte" | "tinyint" | "short" | "smallint" | "char" | "integer" ... > 10:24:02,219 INFO [org.teiid.RUNTIME] (MSC service thread 1-6) TEIID50029 VDB texttab.1 model "model5" metadata is currently being loaded. Start Time: 8/1/16 10:24 AM > 10:24:02,222 INFO [org.teiid.RUNTIME] (teiid-async-threads - 1) TEIID50030 VDB texttab.1 model "model5" metadata loaded. End Time: 8/1/16 10:24 AM > 10:24:02,298 INFO [org.jboss.as.server] (management-handler-thread - 14) JBAS015865: Replaced deployment "texttabvdb-vdb.xml" with deployment "texttabvdb-vdb.xml" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4368) Fail to deploy VDB with TextTable SELECTOR, ROW DELIMITER, HEADER

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4368?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4368. ----------------------------------- Resolution: Rejected Row delimiter was not added until 8.10 TEIID-3163 and HEADER should appear after the columns: https://teiid.gitbooks.io/documents/content/reference/BNF_for_SQL_Grammar... > Fail to deploy VDB with TextTable SELECTOR, ROW DELIMITER, HEADER > ----------------------------------------------------------------- > > Key: TEIID-4368 > URL: https://issues.jboss.org/browse/TEIID-4368 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7 > Reporter: Lucie Fabrikova > Assignee: Steven Hawkins > Attachments: texttabvdb-vdb.xml > > > Server fails to deploy dynamic vdb with models which contain following TextTable parameters: SELECTOR, ROW DELIMITER, HEADER. > Part of server log: > 10:24:02,171 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "texttabvdb-vdb.xml" (runtime-name: "texttabvdb-vdb.xml") > 10:24:02,213 INFO [org.teiid.RUNTIME] (MSC service thread 1-6) TEIID50029 VDB texttab.1 model "model2" metadata is currently being loaded. Start Time: 8/1/16 10:24 AM > 10:24:02,214 INFO [org.teiid.RUNTIME] (MSC service thread 1-6) TEIID50029 VDB texttab.1 model "model3" metadata is currently being loaded. Start Time: 8/1/16 10:24 AM > 10:24:02,217 WARN [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID50036 VDB texttab.1 model "model2" metadata failed to load. Reason:TEIID30386 org.teiid.api.exception.query.QueryParserException: TEIID31100 Parsing error: Encountered "COLUMNS col1 string [*]ROW[*] DELIMITER 'X'" at line 7, column 59. > Was expecting: "escape" | "no" | "selector" | "skip" | "width" | "delimiter" | "quote" | "header" | "," | "(" ... > 10:24:02,218 WARN [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID50036 VDB texttab.1 model "model3" metadata failed to load. Reason:TEIID30386 org.teiid.api.exception.query.QueryParserException: TEIID31100 Parsing error: Encountered ") COLUMNS a [*]HEADER[*] 'a' string" at line 7, column 52. > Was expecting: "string" | "varbinary" | "varchar" | "boolean" | "byte" | "tinyint" | "short" | "smallint" | "char" | "integer" ... > 10:24:02,219 INFO [org.teiid.RUNTIME] (MSC service thread 1-6) TEIID50029 VDB texttab.1 model "model5" metadata is currently being loaded. Start Time: 8/1/16 10:24 AM > 10:24:02,222 INFO [org.teiid.RUNTIME] (teiid-async-threads - 1) TEIID50030 VDB texttab.1 model "model5" metadata loaded. End Time: 8/1/16 10:24 AM > 10:24:02,298 INFO [org.jboss.as.server] (management-handler-thread - 14) JBAS015865: Replaced deployment "texttabvdb-vdb.xml" with deployment "texttabvdb-vdb.xml" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4369) Create translator for HL7

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-4369: ----------------------------------- Summary: Create translator for HL7 Key: TEIID-4369 URL: https://issues.jboss.org/browse/TEIID-4369 Project: Teiid Issue Type: Feature Request Components: Misc. Connectors Reporter: Ramesh Reddy HL7 is Health Data Exchange format, it has been asked couple times about support of this format in Teiid. What it is : http://www.fortherecordmag.com/archives/ftr_01082007p22.shtml This may be spec: http://www.hl7.org/implement/standards/product_brief.cfm?product_id=261 At first glance these format looked more like events, which may not be better suited for Teiid consumption. Some exploration needed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4366) Provide CORS support on OData Service

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4366?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-4366: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1364508 Bugzilla Update: Perform > Provide CORS support on OData Service > ------------------------------------- > > Key: TEIID-4366 > URL: https://issues.jboss.org/browse/TEIID-4366 > Project: Teiid > Issue Type: Enhancement > Components: OData > Affects Versions: 8.12 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Alpha3 > Fix For: 9.1 > > > Good write up CORS can be found here https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS > OData needs to implement CORS support to be valuable with java script based client development technologies. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4366) Provide CORS support on OData Service

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4366?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4366: ------------------------------------- BTW, an example AngularJS client for VDB loopy-vdb.xml (a simple mock vdb) {code} <vdb name="loopy" version="1"> <model visible="true" name="PM1"> <source name="loop" translator-name="loop"/> <metadata type = "DDL"><![CDATA[ CREATE FOREIGN TABLE G1 (e1 integer PRIMARY KEY, e2 varchar(25), e3 double); CREATE FOREIGN TABLE G2 (e1 integer PRIMARY KEY, e2 varchar(25), e3 double, e4 integer, FOREIGN KEY (e4) REFERENCES G1 (e1)); ]]> </metadata> </model> <translator name="loop" type="loopback"> <property name="IncrementRows" value="true"/> <property name="RowCount" value="10"/> </translator> </vdb> {code} AngularJS client test.html {code} <html ng-app=ODataApp> <head> <title>Example to Consume web service from AngularJS App</title> <script src="https://ajax.googleapis.com/ajax/libs/angularjs/1.2.23/angular.min.js"></script> <script type="text/javascript"> var app = angular.module('ODataApp', []); app.controller('ODataController', function($scope, $http) { $http.defaults.headers.common.Authorization = 'Basic dXNlcjpyZWRoYXQxIQ=='; $http.defaults.headers.common.Accept = 'application/json'; $http({ method: 'GET', url: 'http://localhost:8080/odata4/loopy.1/PM1/G1'}) .then(function mySucess(response) { $scope.data = response.data; // this callback will be called asynchronously // when the response is available }, function myerror(response) { alert(response.status); // called asynchronously if an error occurs // or server returns response with an error status. }); }); </script> </head> <body> <div ng-controller="ODataController"> <table> <tr> <th>e1</th> <th>e2</th> </tr> <tr ng-repeat="row in data.value"> <td>{{ row.e1 }}</td> <td>{{ row.e2 }}</td> </tr> </table> </div> </body> </html> {code} > Provide CORS support on OData Service > ------------------------------------- > > Key: TEIID-4366 > URL: https://issues.jboss.org/browse/TEIID-4366 > Project: Teiid > Issue Type: Enhancement > Components: OData > Affects Versions: 8.12 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Alpha3 > Fix For: 9.1 > > > Good write up CORS can be found here https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS > OData needs to implement CORS support to be valuable with java script based client development technologies. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4366) Provide CORS support on OData Service

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4366?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-4366. --------------------------------- Fix Version/s: 9.1 Resolution: Done Labels: Alpha3 (was: ) Added CORS based Servlet filter that adds in required headers for supporting "OPTIONS" method on a call. This is generic, but will work fine in most of the OData specific calls. > Provide CORS support on OData Service > ------------------------------------- > > Key: TEIID-4366 > URL: https://issues.jboss.org/browse/TEIID-4366 > Project: Teiid > Issue Type: Enhancement > Components: OData > Affects Versions: 8.12 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Alpha3 > Fix For: 9.1 > > > Good write up CORS can be found here https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS > OData needs to implement CORS support to be valuable with java script based client development technologies. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3559) Refactor Object and Infinispan translator / connectors

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3559?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3559: ------------------------------------------------ Juraj Duráni <jdurani(a)redhat.com> changed the Status of [bug 1197789|https://bugzilla.redhat.com/show_bug.cgi?id=1197789] from ON_QA to ASSIGNED > Refactor Object and Infinispan translator / connectors > ------------------------------------------------------ > > Key: TEIID-3559 > URL: https://issues.jboss.org/browse/TEIID-3559 > Project: Teiid > Issue Type: Task > Components: Misc. Connectors > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Optional > Fix For: 9.0, 8.12.5 > > > Now that JDG has reworked its remote-cache and changed (reduced) what dependencies its exposed, there's now more common code between the object/infinispan-cache translator/connector and the infinispan-cache-dsl translator/connector. I think refactoring can eliminate issues with support and ensure common behavior across all the code. > Where is common code seen: > - searching (i.e., DSLSearch) > - updates (InfinispanUpdateExecution) > - ClassRegistry > (for starters) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4368) Fail to deploy VDB with TextTable SELECTOR, ROW DELIMITER, HEADER

by Lucie Fabrikova (JIRA)

Lucie Fabrikova created TEIID-4368: -------------------------------------- Summary: Fail to deploy VDB with TextTable SELECTOR, ROW DELIMITER, HEADER Key: TEIID-4368 URL: https://issues.jboss.org/browse/TEIID-4368 Project: Teiid Issue Type: Bug Affects Versions: 8.7 Reporter: Lucie Fabrikova Assignee: Steven Hawkins Attachments: texttabvdb-vdb.xml Server fails to deploy dynamic vdb with models which contain following TextTable parameters: SELECTOR, ROW DELIMITER, HEADER. Part of server log: 10:24:02,171 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "texttabvdb-vdb.xml" (runtime-name: "texttabvdb-vdb.xml") 10:24:02,213 INFO [org.teiid.RUNTIME] (MSC service thread 1-6) TEIID50029 VDB texttab.1 model "model2" metadata is currently being loaded. Start Time: 8/1/16 10:24 AM 10:24:02,214 INFO [org.teiid.RUNTIME] (MSC service thread 1-6) TEIID50029 VDB texttab.1 model "model3" metadata is currently being loaded. Start Time: 8/1/16 10:24 AM 10:24:02,217 WARN [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID50036 VDB texttab.1 model "model2" metadata failed to load. Reason:TEIID30386 org.teiid.api.exception.query.QueryParserException: TEIID31100 Parsing error: Encountered "COLUMNS col1 string [*]ROW[*] DELIMITER 'X'" at line 7, column 59. Was expecting: "escape" | "no" | "selector" | "skip" | "width" | "delimiter" | "quote" | "header" | "," | "(" ... 10:24:02,218 WARN [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID50036 VDB texttab.1 model "model3" metadata failed to load. Reason:TEIID30386 org.teiid.api.exception.query.QueryParserException: TEIID31100 Parsing error: Encountered ") COLUMNS a [*]HEADER[*] 'a' string" at line 7, column 52. Was expecting: "string" | "varbinary" | "varchar" | "boolean" | "byte" | "tinyint" | "short" | "smallint" | "char" | "integer" ... 10:24:02,219 INFO [org.teiid.RUNTIME] (MSC service thread 1-6) TEIID50029 VDB texttab.1 model "model5" metadata is currently being loaded. Start Time: 8/1/16 10:24 AM 10:24:02,222 INFO [org.teiid.RUNTIME] (teiid-async-threads - 1) TEIID50030 VDB texttab.1 model "model5" metadata loaded. End Time: 8/1/16 10:24 AM 10:24:02,298 INFO [org.jboss.as.server] (management-handler-thread - 14) JBAS015865: Replaced deployment "texttabvdb-vdb.xml" with deployment "texttabvdb-vdb.xml" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues August 2016