[JBoss JIRA] (TEIID-3217) XMLTable type conversions result in npe
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-3217:
-------------------------------------
Summary: XMLTable type conversions result in npe
Key: TEIID-3217
URL: https://issues.jboss.org/browse/TEIID-3217
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 8.9
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.9
We are creating an empty set of conversion rules which results in an npe when doing a conversion to a numeric type.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (TEIID-3215) External Materialization ON_VDB_START_SCRIPT invocation issues
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3215?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3215:
-------------------------------------
please add your sample vdb and or testcase
> External Materialization ON_VDB_START_SCRIPT invocation issues
> --------------------------------------------------------------
>
> Key: TEIID-3215
> URL: https://issues.jboss.org/browse/TEIID-3215
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
>
> With materialized view I have set teiid_rel:ON_VDB_START_SCRIPT property for the external matview table. (Simple query to increment a column in table to count invocations.)
> Invocation of the script is dependent upon the way the vdb is deployed. The first case (A) doesn't invoke the script, the second (B) does.
> A - 1. Copy the vdbname-vdb.xml into deployments folder
> 2. Start the server
> B - 1. Start the server
> 2. Copy the vdbname-vdb.xml into deployments folder
> That means that after server stop (maintenance) the script is not invoked on start, which can cause problems when the script is used to initialize running environment (clear table, create temporary table natively,...)
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (TEIID-3214) Dynamic vdb is redeployed twice
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3214?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3214:
-------------------------------------
The ".dodeploy" file something a user creates to deploy an artifact. A ".deploy" is an artifact file created by the JBoss EAP for management of that deployment.
The recommended way to deploy an artifact is using
* web-console
* CLI
* Admin Shell
* Designer (during development)
* creating the ".dodeploy" file.
When you try to re-deploy/re-load without using known/recommended ways, we do not know how the JBoss EAP internals react to that change. All Teiid knows, it got a deployment event for that artifact. Clearly ".deploy" files are there for management of the artifacts after deployment for consistent behavior across domain, not for re-deploy purpose. There is README.txt file in the "deployments" folder of the EAP, please read that for correct ways to do a deployment.
Based on above, I am inclined to reject this JIRA
> Dynamic vdb is redeployed twice
> -------------------------------
>
> Key: TEIID-3214
> URL: https://issues.jboss.org/browse/TEIID-3214
> Project: Teiid
> Issue Type: Bug
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
>
> I have a dynamic vdb. When I redeploy it with command 'touch vdbname-vdb.xml.deployed' then the vdb is redeployed twice within 5 seconds. Whole the procedure runs twice - see the log in the end of description. When the vdb is redeployed by 'touch vdbname-vdb.xml' everything is fine. Happens only with dynamic vdbs, static vdbs and wars,etc work fine.
> Log:
> 09:23:13,599 INFO [org.teiid.RUNTIME] (MSC service thread 1-4) TEIID50026 VDB "mat-views.1[Source{Source=Source, h2-override, java:/mat-views-ds}, View{}]" undeployed.
> 09:23:13,604 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment mat-views-vdb.xml (runtime-name: mat-views-vdb.xml) in 7ms
> 09:23:13,604 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "mat-views-vdb.xml" (runtime-name: "mat-views-vdb.xml")
> 09:23:13,629 INFO [org.teiid.SECURITY] (MSC service thread 1-1) TEIID40009 Admin [null] is terminating this session: ItnNDZmYCq/y.
> 09:23:13,633 INFO [org.teiid.RUNTIME] (MSC service thread 1-1) TEIID50029 VDB mat-views.1 model "Source" metadata is currently being loaded. Start Time: 11/13/14 9:23 AM
> 09:23:13,634 INFO [org.teiid.RUNTIME] (MSC service thread 1-1) TEIID50029 VDB mat-views.1 model "View" metadata is currently being loaded. Start Time: 11/13/14 9:23 AM
> 09:23:13,634 INFO [org.teiid.CONNECTOR] (teiid-async-threads - 3) H2ExecutionFactory Commit=true;DatabaseProductName=H2;DatabaseProductVersion=@PROJECT_VERSION@ (2012-07-13);DriverMajorVersion=1;DriverMajorVersion=3;DriverName=H2 JDBC Driver;DriverVersion=@PROJECT_VERSION@ (2012-07-13);IsolationLevel=2
> 09:23:13,636 INFO [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID50030 VDB mat-views.1 model "View" metadata loaded. End Time: 11/13/14 9:23 AM
> 09:23:13,683 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018562: Redeployed "mat-views-vdb.xml"
> 09:23:13,840 INFO [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID50030 VDB mat-views.1 model "Source" metadata loaded. End Time: 11/13/14 9:23 AM
> 09:23:13,846 INFO [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID40003 VDB mat-views.1 is set to ACTIVE
> 09:23:18,757 INFO [org.teiid.RUNTIME] (MSC service thread 1-1) TEIID50026 VDB "mat-views.1[Source{Source=Source, h2-override, java:/mat-views-ds}, View{}]" undeployed.
> 09:23:18,760 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015877: Stopped deployment mat-views-vdb.xml (runtime-name: mat-views-vdb.xml) in 4ms
> 09:23:18,761 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "mat-views-vdb.xml" (runtime-name: "mat-views-vdb.xml")
> 09:23:18,789 INFO [org.teiid.RUNTIME] (MSC service thread 1-8) TEIID50029 VDB mat-views.1 model "Source" metadata is currently being loaded. Start Time: 11/13/14 9:23 AM
> 09:23:18,791 INFO [org.teiid.RUNTIME] (MSC service thread 1-8) TEIID50029 VDB mat-views.1 model "View" metadata is currently being loaded. Start Time: 11/13/14 9:23 AM
> 09:23:18,795 INFO [org.teiid.CONNECTOR] (teiid-async-threads - 2) H2ExecutionFactory Commit=true;DatabaseProductName=H2;DatabaseProductVersion=@PROJECT_VERSION@ (2012-07-13);DriverMajorVersion=1;DriverMajorVersion=3;DriverName=H2 JDBC Driver;DriverVersion=@PROJECT_VERSION@ (2012-07-13);IsolationLevel=2
> 09:23:18,807 INFO [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID50030 VDB mat-views.1 model "View" metadata loaded. End Time: 11/13/14 9:23 AM
> 09:23:18,820 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018565: Replaced deployment "mat-views-vdb.xml" with deployment "mat-views-vdb.xml"
> 09:23:18,999 INFO [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID50030 VDB mat-views.1 model "Source" metadata loaded. End Time: 11/13/14 9:23 AM
> 09:23:19,005 INFO [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID40003 VDB mat-views.1 is set to ACTIVE
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (TEIID-3214) Dynamic vdb is redeployed twice
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-3214?page=com.atlassian.jira.plugin... ]
Van Halbert commented on TEIID-3214:
------------------------------------
Should we worry about this since touching the .deployed file isn't a recommend way of deployment. And if there are changes, it normally is to the -vdb.xml, which does trigger the correct behavior.
> Dynamic vdb is redeployed twice
> -------------------------------
>
> Key: TEIID-3214
> URL: https://issues.jboss.org/browse/TEIID-3214
> Project: Teiid
> Issue Type: Bug
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
>
> I have a dynamic vdb. When I redeploy it with command 'touch vdbname-vdb.xml.deployed' then the vdb is redeployed twice within 5 seconds. Whole the procedure runs twice - see the log in the end of description. When the vdb is redeployed by 'touch vdbname-vdb.xml' everything is fine. Happens only with dynamic vdbs, static vdbs and wars,etc work fine.
> Log:
> 09:23:13,599 INFO [org.teiid.RUNTIME] (MSC service thread 1-4) TEIID50026 VDB "mat-views.1[Source{Source=Source, h2-override, java:/mat-views-ds}, View{}]" undeployed.
> 09:23:13,604 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment mat-views-vdb.xml (runtime-name: mat-views-vdb.xml) in 7ms
> 09:23:13,604 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "mat-views-vdb.xml" (runtime-name: "mat-views-vdb.xml")
> 09:23:13,629 INFO [org.teiid.SECURITY] (MSC service thread 1-1) TEIID40009 Admin [null] is terminating this session: ItnNDZmYCq/y.
> 09:23:13,633 INFO [org.teiid.RUNTIME] (MSC service thread 1-1) TEIID50029 VDB mat-views.1 model "Source" metadata is currently being loaded. Start Time: 11/13/14 9:23 AM
> 09:23:13,634 INFO [org.teiid.RUNTIME] (MSC service thread 1-1) TEIID50029 VDB mat-views.1 model "View" metadata is currently being loaded. Start Time: 11/13/14 9:23 AM
> 09:23:13,634 INFO [org.teiid.CONNECTOR] (teiid-async-threads - 3) H2ExecutionFactory Commit=true;DatabaseProductName=H2;DatabaseProductVersion=@PROJECT_VERSION@ (2012-07-13);DriverMajorVersion=1;DriverMajorVersion=3;DriverName=H2 JDBC Driver;DriverVersion=@PROJECT_VERSION@ (2012-07-13);IsolationLevel=2
> 09:23:13,636 INFO [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID50030 VDB mat-views.1 model "View" metadata loaded. End Time: 11/13/14 9:23 AM
> 09:23:13,683 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018562: Redeployed "mat-views-vdb.xml"
> 09:23:13,840 INFO [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID50030 VDB mat-views.1 model "Source" metadata loaded. End Time: 11/13/14 9:23 AM
> 09:23:13,846 INFO [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID40003 VDB mat-views.1 is set to ACTIVE
> 09:23:18,757 INFO [org.teiid.RUNTIME] (MSC service thread 1-1) TEIID50026 VDB "mat-views.1[Source{Source=Source, h2-override, java:/mat-views-ds}, View{}]" undeployed.
> 09:23:18,760 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015877: Stopped deployment mat-views-vdb.xml (runtime-name: mat-views-vdb.xml) in 4ms
> 09:23:18,761 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "mat-views-vdb.xml" (runtime-name: "mat-views-vdb.xml")
> 09:23:18,789 INFO [org.teiid.RUNTIME] (MSC service thread 1-8) TEIID50029 VDB mat-views.1 model "Source" metadata is currently being loaded. Start Time: 11/13/14 9:23 AM
> 09:23:18,791 INFO [org.teiid.RUNTIME] (MSC service thread 1-8) TEIID50029 VDB mat-views.1 model "View" metadata is currently being loaded. Start Time: 11/13/14 9:23 AM
> 09:23:18,795 INFO [org.teiid.CONNECTOR] (teiid-async-threads - 2) H2ExecutionFactory Commit=true;DatabaseProductName=H2;DatabaseProductVersion=@PROJECT_VERSION@ (2012-07-13);DriverMajorVersion=1;DriverMajorVersion=3;DriverName=H2 JDBC Driver;DriverVersion=@PROJECT_VERSION@ (2012-07-13);IsolationLevel=2
> 09:23:18,807 INFO [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID50030 VDB mat-views.1 model "View" metadata loaded. End Time: 11/13/14 9:23 AM
> 09:23:18,820 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018565: Replaced deployment "mat-views-vdb.xml" with deployment "mat-views-vdb.xml"
> 09:23:18,999 INFO [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID50030 VDB mat-views.1 model "Source" metadata loaded. End Time: 11/13/14 9:23 AM
> 09:23:19,005 INFO [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID40003 VDB mat-views.1 is set to ACTIVE
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (TEIID-3213) Getting error when running adminshell load {script}
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3213?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3213.
-----------------------------------
Resolution: Done
> Getting error when running adminshell load {script}
> ---------------------------------------------------
>
> Key: TEIID-3213
> URL: https://issues.jboss.org/browse/TEIID-3213
> Project: Teiid
> Issue Type: Bug
> Components: Tools
> Affects Versions: 8.9
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Fix For: 8.9
>
>
> Running the 8.10 beta adminshell and getting the following error when running one of the examples:
> ./adminshell.sh load ./examples/PrintAllVDBAndDatasources.groovy
> ===> static org.teiid.adminshell.AdminShell.*
> ===> static org.teiid.adminshell.AdminShell.*, static org.teiid.adminshell.GroovySqlExtensions.*
> ===> static org.teiid.adminshell.AdminShell.*, static org.teiid.adminshell.GroovySqlExtensions.*, org.teiid.adminapi.*
> FATAL: groovy.lang.MissingPropertyException: No such property: load for class: groovysh_evaluate
> groovy.lang.MissingPropertyException: No such property: load for class: groovysh_evaluate
> at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:50)
> at org.codehaus.groovy.runtime.callsite.PogoGetPropertySite.getProperty(PogoGetPropertySite.java:49)
> at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callGroovyObjectGetProperty(AbstractCallSite.java:231)
> at groovysh_evaluate.run(groovysh_evaluate:3)
> at groovysh_evaluate$run.call(Unknown Source)
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (TEIID-3216) Implement INSERT, UPDATE and DELETE support for google-spreadsheet connector
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3216?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3216:
---------------------------------------
On consistency, the Salesforce bulk insert has the same non-atomic behavior. Just make sure that the update count array contains the appropriate 1 (success), -3 (Statement.EXECUTE_FAILED), or -2 (Statement.SUCCESS_NO_INFO) for each record.
> Implement INSERT, UPDATE and DELETE support for google-spreadsheet connector
> ----------------------------------------------------------------------------
>
> Key: TEIID-3216
> URL: https://issues.jboss.org/browse/TEIID-3216
> Project: Teiid
> Issue Type: Task
> Components: Misc. Connectors
> Reporter: Filip Elias
> Assignee: Filip Elias
> Fix For: Open To Community
>
>
> Current plan is to use list-based feed of the Google Data API[1].
> There are three known issues:
> performance - to delete/update 100 rows Teiid must generate 100 http requests
> consistency - user wants to update 50 rows. After the 10th row is updated the connection could fail which would cause that 10 rows would be updated and 40 wouldn't.
> headers - update, delete and and insert statements will be supported only for the spreadsheets that have a header for each column (headers are in the first row of a spreadsheet)
> Select statement is implemented using Google Visualisation API, but this API doesn't support updates and doesn't return row numbers.
> [1] https://developers.google.com/google-apps/spreadsheets/
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (TEIID-3216) Implement INSERT, UPDATE and DELETE support for google-spreadsheet connector
by Filip Elias (JIRA)
[ https://issues.jboss.org/browse/TEIID-3216?page=com.atlassian.jira.plugin... ]
Filip Elias updated TEIID-3216:
-------------------------------
Fix Version/s: Open To Community
> Implement INSERT, UPDATE and DELETE support for google-spreadsheet connector
> ----------------------------------------------------------------------------
>
> Key: TEIID-3216
> URL: https://issues.jboss.org/browse/TEIID-3216
> Project: Teiid
> Issue Type: Task
> Components: Misc. Connectors
> Reporter: Filip Elias
> Assignee: Filip Elias
> Fix For: Open To Community
>
>
> Current plan is to use list-based feed of the Google Data API[1].
> There are three known issues:
> performance - to delete/update 100 rows Teiid must generate 100 http requests
> consistency - user wants to update 50 rows. After the 10th row is updated the connection could fail which would cause that 10 rows would be updated and 40 wouldn't.
> headers - update, delete and and insert statements will be supported only for the spreadsheets that have a header for each column (headers are in the first row of a spreadsheet)
> Select statement is implemented using Google Visualisation API, but this API doesn't support updates and doesn't return row numbers.
> [1] https://developers.google.com/google-apps/spreadsheets/
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (TEIID-3216) Implement INSERT, UPDATE and DELETE support for google-spreadsheet connector
by Filip Elias (JIRA)
Filip Elias created TEIID-3216:
----------------------------------
Summary: Implement INSERT, UPDATE and DELETE support for google-spreadsheet connector
Key: TEIID-3216
URL: https://issues.jboss.org/browse/TEIID-3216
Project: Teiid
Issue Type: Task
Components: Misc. Connectors
Reporter: Filip Elias
Assignee: Filip Elias
Current plan is to use list-based feed of the Google Data API[1].
There are three known issues:
performance - to delete/update 100 rows Teiid must generate 100 http requests
consistency - user wants to update 50 rows. After the 10th row is updated the connection could fail which would cause that 10 rows would be updated and 40 wouldn't.
headers - update, delete and and insert statements will be supported only for the spreadsheets that have a header for each column (headers are in the first row of a spreadsheet)
Select statement is implemented using Google Visualisation API, but this API doesn't support updates and doesn't return row numbers.
[1] https://developers.google.com/google-apps/spreadsheets/
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (TEIID-3215) External Materialization ON_VDB_START_SCRIPT invocation issues
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3215?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-3215:
-------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1163685
> External Materialization ON_VDB_START_SCRIPT invocation issues
> --------------------------------------------------------------
>
> Key: TEIID-3215
> URL: https://issues.jboss.org/browse/TEIID-3215
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
>
> With materialized view I have set teiid_rel:ON_VDB_START_SCRIPT property for the external matview table. (Simple query to increment a column in table to count invocations.)
> Invocation of the script is dependent upon the way the vdb is deployed. The first case (A) doesn't invoke the script, the second (B) does.
> A - 1. Copy the vdbname-vdb.xml into deployments folder
> 2. Start the server
> B - 1. Start the server
> 2. Copy the vdbname-vdb.xml into deployments folder
> That means that after server stop (maintenance) the script is not invoked on start, which can cause problems when the script is used to initialize running environment (clear table, create temporary table natively,...)
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (TEIID-3215) External Materialization ON_VDB_START_SCRIPT invocation issues
by Jan Stastny (JIRA)
Jan Stastny created TEIID-3215:
----------------------------------
Summary: External Materialization ON_VDB_START_SCRIPT invocation issues
Key: TEIID-3215
URL: https://issues.jboss.org/browse/TEIID-3215
Project: Teiid
Issue Type: Bug
Affects Versions: 8.7
Reporter: Jan Stastny
Assignee: Steven Hawkins
With materialized view I have set teiid_rel:ON_VDB_START_SCRIPT property for the external matview table. (Simple query to increment a column in table to count invocations.)
Invocation of the script is dependent upon the way the vdb is deployed. The first case (A) doesn't invoke the script, the second (B) does.
A - 1. Copy the vdbname-vdb.xml into deployments folder
2. Start the server
B - 1. Start the server
2. Copy the vdbname-vdb.xml into deployments folder
That means that after server stop (maintenance) the script is not invoked on start, which can cause problems when the script is used to initialize running environment (clear table, create temporary table natively,...)
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month