[JBoss JIRA] Commented: (TEIID-1355) adminshell.bat cannot read script from stdin
by Steven Hawkins (JIRA)
[ https://jira.jboss.org/browse/TEIID-1355?page=com.atlassian.jira.plugin.s... ]
Steven Hawkins commented on TEIID-1355:
---------------------------------------
The difference is probably in the shell behavior. The launching scripts are not really any different and just launch the same main. Anything piped in via a unix like shell is getting properly converted to a string prior to execution. This must not be the case on windows. I couldn't find any description of this problem with windows scripts with just a cursory search. Do we have any windows scripting experts that could weigh in?
> adminshell.bat cannot read script from stdin
> --------------------------------------------
>
> Key: TEIID-1355
> URL: https://jira.jboss.org/browse/TEIID-1355
> Project: Teiid
> Issue Type: Bug
> Components: Tools
> Affects Versions: 7.1
> Environment: windows
> Reporter: Aleksandar Kostadinov
>
> On windows adminshell doesn't read script if supplied on stdin. It looks like it is reading from terminal (unlike adminshell on linux). I see that one can supply expression as first argument to adminshell but it seems to accept only a single expression and additionally complex expressions are a hell to escape properly.
> Assuming adminshell is intended to be used for automating administrative tasks, it needs a straightforward way to execute scripts non-interactively so current behavior on windows needs to be fixed.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 4 months
[JBoss JIRA] Commented: (TEIID-1355) adminshell.bat cannot read script from stdin
by Ramesh Reddy (JIRA)
[ https://jira.jboss.org/browse/TEIID-1355?page=com.atlassian.jira.plugin.s... ]
Ramesh Reddy commented on TEIID-1355:
-------------------------------------
Again, Groovy is NOT developed by JBoss nor Teiid. This is another community project. Teiid uses as its shell environment because we feel that the features it provides is sufficient *enough* for our uses. I still do not get what you are asking for. You can execute
adminshell.bat print 'hello' --> to execute the the commands inline
or
adminshell.bat load test.txt
where the "test.txt" has the commands. The "load" command is documented with Groovy, As per the instructions here they are documented http://docs.jboss.org/teiid/7.2.0.Final/admin-guide/en-US/html_single/#d0... are these not enough?
> adminshell.bat cannot read script from stdin
> --------------------------------------------
>
> Key: TEIID-1355
> URL: https://jira.jboss.org/browse/TEIID-1355
> Project: Teiid
> Issue Type: Bug
> Components: Tools
> Affects Versions: 7.1
> Environment: windows
> Reporter: Aleksandar Kostadinov
>
> On windows adminshell doesn't read script if supplied on stdin. It looks like it is reading from terminal (unlike adminshell on linux). I see that one can supply expression as first argument to adminshell but it seems to accept only a single expression and additionally complex expressions are a hell to escape properly.
> Assuming adminshell is intended to be used for automating administrative tasks, it needs a straightforward way to execute scripts non-interactively so current behavior on windows needs to be fixed.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 4 months
[JBoss JIRA] Moved: (TEIID-1363) Strange value for "Max Rows Fetch Size" in Data Services configuration.
by Van Halbert (JIRA)
[ https://jira.jboss.org/browse/TEIID-1363?page=com.atlassian.jira.plugin.s... ]
Van Halbert moved SOA-2596 to TEIID-1363:
-----------------------------------------
Project: Teiid (was: JBoss Enterprise SOA Platform)
Key: TEIID-1363 (was: SOA-2596)
Affects Version/s: 7.1.1
(was: 5.1.0.ER4)
Security: (was: Public)
Component/s: Jopr Plugin
(was: EDS)
> Strange value for "Max Rows Fetch Size" in Data Services configuration.
> -----------------------------------------------------------------------
>
> Key: TEIID-1363
> URL: https://jira.jboss.org/browse/TEIID-1363
> Project: Teiid
> Issue Type: Bug
> Components: Jopr Plugin
> Affects Versions: 7.1.1
> Reporter: Jehudi Castro
> Attachments: Screenshot-JBoss SOA Admin Console - Mozilla Firefox-1.png
>
>
> On the admin console, "Data Services" node and Configuration option the value for "Max Rows Fetch Size" is 20480 this looks like a typo of 2048, anyway it differs from the so called default value of 1024 according to the column just at the right.
> Same with Prepared Plan Cache Max Count, "default" claims to be 250, but the actual value is 512
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 4 months
[JBoss JIRA] Resolved: (TEIID-211) subquery optimization
by Steven Hawkins (JIRA)
[ https://jira.jboss.org/browse/TEIID-211?page=com.atlassian.jira.plugin.sy... ]
Steven Hawkins resolved TEIID-211.
----------------------------------
Resolution: Done
Added rewrite handling for where subqueries that are correlated against unique values from the outer query. Also added cost based semi and anti semi join handling for non-pushed subqueries.
TODO:
makedep hint on a subquery
rewrite select scalar subqueries
rewrite subqueries in the on clause
better null detection for not conditions
better unique detection (right now we're restricted to simple queries and and key columns)
> subquery optimization
> ---------------------
>
> Key: TEIID-211
> URL: https://jira.jboss.org/browse/TEIID-211
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Affects Versions: 6.0.0
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 7.3
>
>
> Implement rewriter (and planner) optimizations for subqueries based upon semi and anti semi join capabilities.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 4 months
[JBoss JIRA] Commented: (TEIID-1355) adminshell.bat cannot read script from stdin
by Aleksandar Kostadinov (JIRA)
[ https://jira.jboss.org/browse/TEIID-1355?page=com.atlassian.jira.plugin.s... ]
Aleksandar Kostadinov commented on TEIID-1355:
----------------------------------------------
On linux if you pass a script to stdin of the the adminshell process it gets executed.
echo "println 'hello'" | adminshell.sh
Of course more complicated scripts are also possible. Given it is possible to load a file then the critical functionality is present but it just feels inflexible to be unable to write "adminshell.bat < myscript.groovy" or "type myscript1.groovy myscript2.groovy | adminshell.bat".
Anyways if it is not hart to make reading a script from stdin work, then I think it is a good idea to fix that. Otherwise executing a script file non-interactively may just be documented.
Thanks!
> adminshell.bat cannot read script from stdin
> --------------------------------------------
>
> Key: TEIID-1355
> URL: https://jira.jboss.org/browse/TEIID-1355
> Project: Teiid
> Issue Type: Bug
> Components: Tools
> Affects Versions: 7.1
> Environment: windows
> Reporter: Aleksandar Kostadinov
>
> On windows adminshell doesn't read script if supplied on stdin. It looks like it is reading from terminal (unlike adminshell on linux). I see that one can supply expression as first argument to adminshell but it seems to accept only a single expression and additionally complex expressions are a hell to escape properly.
> Assuming adminshell is intended to be used for automating administrative tasks, it needs a straightforward way to execute scripts non-interactively so current behavior on windows needs to be fixed.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 5 months
[JBoss JIRA] Issue Comment Edited: (TEIID-999) Create valid capabilities support for MS Excel and MS Access JDBC-ODBC Connectors
by Warren Gibson (JIRA)
[ https://jira.jboss.org/browse/TEIID-999?page=com.atlassian.jira.plugin.sy... ]
Warren Gibson edited comment on TEIID-999 at 11/15/10 8:56 PM:
---------------------------------------------------------------
11-15-2010 WG - I was able to connect a Excel/Access source to a Teiid VDB and query it using the following steps.
ODBC Excel/Access as a Teiid source Test
Environment: Windows with Excel/Access 2003 or later, designer installed, Teiid installed, and a jdbc client such as Squirrel installed.
1. Open Designer and create a new project.
2. Create a Excel/Access Source Model with a Base Table representing the columns in the Excel/Access files. I used a source model name to match the Excel/Access target source.
3. Create a virtual table with same columns as the base table.
4. Create a vdb for Excel/Access with a unique jndi name. The unique jndi names will also be used in the ds file and as the Windows DSN name. Used jdbc-simple as the Translator.
5. Deployed the vdb to a running Teiid instance.
6. Use the Windows ODBC Data Source Administration tool to create two DSNs pointing to the source files.
7. Create a ds file for Excel/Access using the jndi-name in the vdb. See examples below.
8. Copy ds files to server deploy directory.
9. Use a JDBC client such as Squirrel to query the vdbs. The Teiid client jar (teiid-<x.xx>-client.jar) is used to set up a driver in Squirrel. Connect to vdbs.
(example url:jdbc:teiid:<vdb>@mm://localhost:31000, user name <xxx> and password <xxx>)
10 Queried the source table and virtual table with a good sampling of queries.
DS FILE EXAMPLE Excel
<?xml version="1.0" encoding="UTF-8"?>
<datasources>
<no-tx-datasource>
<jndi-name>ExcelDS</jndi-name>
<connection-url>jdbc:odbc:Driver={Microsoft Excel Driver (*.xls)};Dbq=<url for source file location></connection-url>
<driver-class>sun.jdbc.odbc.JdbcOdbcDriver</driver-class>
<transaction-isolation>TRANSACTION_NONE</transaction-isolation>
<min-pool-size>1</min-pool-size>
<max-pool-size>1</max-pool-size>
<idle-timeout-minutes>5</idle-timeout-minutes>
</no-tx-datasource>
</datasources>
DS FILE EXAMPLE Access
<?xml version="1.0" encoding="UTF-8"?>
<datasources>
<local-tx-datasource>
<jndi-name>AccessDS</jndi-name>
<connection-url>jdbc:odbc:AccessDS</connection-url>
<driver-class>sun.jdbc.odbc.JdbcOdbcDriver</driver-class>
<min-pool-size>1</min-pool-size>
<max-pool-size>1</max-pool-size>
<idle-timeout-minutes>5</idle-timeout-minutes>
</local-tx-datasource>
</datasources>
was (Author: wgibson(a)jboss.org):
11-15-2010 WG - I was able to connect a Excel/Access source to a Teiid VDB and query it using the following steps.
ODBC Excel/Access as a Teiid source Test
Environment: Windows with Excel/Access 2003 or later, designer installed, Teiid installed, and a jdbc client such as Squirrel installed.
1. Open Designer and create a new project.
2. Create a Excel/Access Source Model with a Base Table representing the columns in the Excel/Access files. I used a source model name to match the Excel/Access target source.
3. Create a virtual table with same columns as the base table.
4. Create a vdb for Excel/Access with a unique jndi name. The unique jndi names will also be used in the ds file and as the Windows DSN name. Used jdbc-simple as the Translator.
5. Deployed the vdb to a running Teiid instance.
6. Use the Windows ODBC Data Source Administration tool to create two DSNs pointing to the source files.
7. Create a ds file for Excel/Access using the jndi-name in the vdb. See examples below.
8. Copy ds files to server deploy directory.
9. Use a JDBC client such as Squirrel to query the vdbs. The Teiid client jar (teiid-<x.xx>-client.jar) is used to set up a driver in Squirrel. Connect to vdbs.
(example url:jdbc:teiid:<vdb>@mm://localhost:31000, user name <xxx> and password <xxx>)
10 Queried the source table and virtual table with a good sampling of queries.
DS FILE EXAMPLE Excel
<?xml version="1.0" encoding="UTF-8"?>
<datasources>
<no-tx-datasource>
<jndi-name>ExcelDS</jndi-name>
<connection-url>jdbc:odbc:Driver={Microsoft Excel Driver (*.xls)};Dbq=<url for source file location></connection-url>
<driver-class>sun.jdbc.odbc.JdbcOdbcDriver</driver-class>
<transaction-isolation>TRANSACTION_NONE</transaction-isolation>
<min-pool-size>1</min-pool-size>
<max-pool-size>1</max-pool-size>
<idle-timeout-minutes>5</idle-timeout-minutes>
</no-tx-datasource>
</datasources>
DS FILE EXAMPLE Access
<?xml version="1.0" encoding="UTF-8"?>
<datasources>
<local-tx-datasource>
<jndi-name>AccessDS</jndi-name>
<connection-url>jdbc:odbc:AccessDS</connection-url>
<driver-class>sun.jdbc.odbc.JdbcOdbcDriver</driver-class>
<min-pool-size>1</min-pool-size>
<max-pool-size>1</max-pool-size>
<idle-timeout-minutes>5</idle-timeout-minutes>
</local-tx-datasource>
</datasources>
> Create valid capabilities support for MS Excel and MS Access JDBC-ODBC Connectors
> ---------------------------------------------------------------------------------
>
> Key: TEIID-999
> URL: https://jira.jboss.org/browse/TEIID-999
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Environment: MS Excel 2003
> Reporter: Larry O'Leary
> Fix For: 8.0
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> Create a capabilities set that can be used by the MS Access and MS Excel connectors. We currently offer the MS Excel connector which is using the generic JDBC capabilities and translators and the MS Access connector which is using its own capabilities and translators but they do not reflect MS Access.
> The replacement connector types should work very much like the current ones but reflect the base capabilities offered by MS JET 4 and specific capabilities as defined by the MS Excel and MS Access limitations to the MS JET 4 implementation. At bare minimum we should support push-down of all currently defined capabilities and remove any current ones that are not valid for MS JET/MS Access/MS Excel.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 5 months
[JBoss JIRA] Commented: (TEIID-999) Create valid capabilities support for MS Excel and MS Access JDBC-ODBC Connectors
by Warren Gibson (JIRA)
[ https://jira.jboss.org/browse/TEIID-999?page=com.atlassian.jira.plugin.sy... ]
Warren Gibson commented on TEIID-999:
-------------------------------------
11-15-2010 WG - I was able to connect a Excel/Access source to a Teiid VDB and query it using the following steps.
ODBC Excel/Access as a Teiid source Test
Environment: Windows with Excel/Access 2003 or later, designer installed, Teiid installed, and a jdbc client such as Squirrel installed.
1. Open Designer and create a new project.
2. Create a Excel/Access Source Model with a Base Table representing the columns in the Excel/Access files. I used a source model name to match the Excel/Access target source.
3. Create a virtual table with same columns as the base table.
4. Create a vdb for Excel/Access with a unique jndi name. The unique jndi names will also be used in the ds file and as the Windows DSN name. Used jdbc-simple as the Translator.
5. Deployed the vdb to a running Teiid instance.
6. Use the Windows ODBC Data Source Administration tool to create two DSNs pointing to the source files.
7. Create a ds file for Excel/Access using the jndi-name in the vdb. See examples below.
8. Copy ds files to server deploy directory.
9. Use a JDBC client such as Squirrel to query the vdbs. The Teiid client jar (teiid-<x.xx>-client.jar) is used to set up a driver in Squirrel. Connect to vdbs.
(example url:jdbc:teiid:<vdb>@mm://localhost:31000, user name <xxx> and password <xxx>)
10 Queried the source table and virtual table with a good sampling of queries.
DS FILE EXAMPLE Excel
<?xml version="1.0" encoding="UTF-8"?>
<datasources>
<no-tx-datasource>
<jndi-name>ExcelDS</jndi-name>
<connection-url>jdbc:odbc:Driver={Microsoft Excel Driver (*.xls)};Dbq=<url for source file location></connection-url>
<driver-class>sun.jdbc.odbc.JdbcOdbcDriver</driver-class>
<transaction-isolation>TRANSACTION_NONE</transaction-isolation>
<min-pool-size>1</min-pool-size>
<max-pool-size>1</max-pool-size>
<idle-timeout-minutes>5</idle-timeout-minutes>
</no-tx-datasource>
</datasources>
DS FILE EXAMPLE Access
<?xml version="1.0" encoding="UTF-8"?>
<datasources>
<local-tx-datasource>
<jndi-name>AccessDS</jndi-name>
<connection-url>jdbc:odbc:AccessDS</connection-url>
<driver-class>sun.jdbc.odbc.JdbcOdbcDriver</driver-class>
<min-pool-size>1</min-pool-size>
<max-pool-size>1</max-pool-size>
<idle-timeout-minutes>5</idle-timeout-minutes>
</local-tx-datasource>
</datasources>
> Create valid capabilities support for MS Excel and MS Access JDBC-ODBC Connectors
> ---------------------------------------------------------------------------------
>
> Key: TEIID-999
> URL: https://jira.jboss.org/browse/TEIID-999
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Environment: MS Excel 2003
> Reporter: Larry O'Leary
> Fix For: 8.0
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> Create a capabilities set that can be used by the MS Access and MS Excel connectors. We currently offer the MS Excel connector which is using the generic JDBC capabilities and translators and the MS Access connector which is using its own capabilities and translators but they do not reflect MS Access.
> The replacement connector types should work very much like the current ones but reflect the base capabilities offered by MS JET 4 and specific capabilities as defined by the MS Excel and MS Access limitations to the MS JET 4 implementation. At bare minimum we should support push-down of all currently defined capabilities and remove any current ones that are not valid for MS JET/MS Access/MS Excel.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 5 months