[JBoss JIRA] (TEIID-2989) Support odata batching
by Madhurika Sharma (JIRA)
[ https://issues.jboss.org/browse/TEIID-2989?page=com.atlassian.jira.plugin... ]
Madhurika Sharma commented on TEIID-2989:
-----------------------------------------
Can you please tell me the link or some documentation where there is a step by step tutorial for OData batching ?
> Support odata batching
> ----------------------
>
> Key: TEIID-2989
> URL: https://issues.jboss.org/browse/TEIID-2989
> Project: Teiid
> Issue Type: Enhancement
> Components: OData
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.8
>
>
> We nearly have support for OData batching, but the ODataBatchingProvider is registered as a class and not as an instance. Otherwise it appears that a multipart/mixed post to an entity/$batch will allow for batching in OData4j.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months
[JBoss JIRA] (TEIID-2992) MongoDB: Offset clause causes MongoDB to crash
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2992?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-2992:
-------------------------------------
Did not realize there is also OFFSET based option where LIMIT number is optional, will correct it
> MongoDB: Offset clause causes MongoDB to crash
> ----------------------------------------------
>
> Key: TEIID-2992
> URL: https://issues.jboss.org/browse/TEIID-2992
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.4.1
> Environment: MongoDB < 2.5.2
> Reporter: Filip Elias
> Assignee: Ramesh Reddy
>
> MongoDB(version < 2.5.2) will crash when offset clause is used in SQL query.
> Althought the bug[1] is in MongoDB (Adding big number into $limit causes Mongodb to shutdown), it is also caused by teiid because it adds max integer into $limit which seems to be unnecessary.
> Sample query:
> {code}
> SELECT INTKEY FROM bqt1.smalla ORDER BY INTKEY OFFSET 45 ROWS
> {code}
> Generated mongo command:
> {code}
> { aggregate: "smalla", pipeline: [ { $project: { c_0: "$INTKEY" } }, { $sort: { c_0: 1 } }, { $skip: 45 }, { $limit: 2147483647 } ] }
> {code}
> [1] https://jira.mongodb.org/browse/SERVER-10136
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months
[JBoss JIRA] (TEIID-2993) Adding source table with quoted name results in wrong generated SQL statement
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2993?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2993:
---------------------------------------
This has been the parsing behavior since the old MMX days. There are a couple of reasons for this. One is that I believe they wanted to support sql written for the target db. Since after import the notions of catalog, schema, and table name can be altered, their idea was to just throw away the user quoting. Then the resolving system matches this perspective by progressively matching against partial names. This of course is not correct from the perspective of Teiid as database and can lead to unexpected ambiguities.
Long story short from a runtime perspective the above is expected behavior.
> Adding source table with quoted name results in wrong generated SQL statement
> -----------------------------------------------------------------------------
>
> Key: TEIID-2993
> URL: https://issues.jboss.org/browse/TEIID-2993
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.7.2, 8.7
> Reporter: Paul Richardson
> Assignee: Steven Hawkins
> Fix For: 8.7.1, 8.8
>
>
> Cloned from TEIIDDES-2152:
> 1) Created source model with simple table named "My.Quoted.Table" (including quotes
> 2) Created simple virtual table and pasted: SELECT * FROM "My.Quoted.Table"
> 3) Parser returned a command resulting in the SQL: SELECT * FROM My.Quoted."Table"
> Parser should be able to handle quoted names properly. In this case the SQL should have been valid as is.
> Confirmed that this does go right back to the Teiid parser. To confirm, the following test was included in
> src/test/java/org/teiid/query/parser/TestParser.java
> {code}
> @Test
> public void testQuotedSQLString() {
> String sql = "SELECT * FROM \"My.Quoted.Table\""; //$NON-NLS-1$
> String expected = "SELECT * FROM \"MY.QUOTED.TABLE\""; //$NON-NLS-1$
> helpTest(sql, expected, null);
> }
> {code}
> Test fails with a comparison error with the parser returning the SQL in item 3 above.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months
[JBoss JIRA] (TEIID-2993) Adding source table with quoted name results in wrong generated SQL statement
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIID-2993?page=com.atlassian.jira.plugin... ]
Paul Richardson updated TEIID-2993:
-----------------------------------
Description:
Cloned from TEIIDDES-2152:
1) Created source model with simple table named "My.Quoted.Table" (including quotes
2) Created simple virtual table and pasted: SELECT * FROM "My.Quoted.Table"
3) Parser returned a command resulting in the SQL: SELECT * FROM My.Quoted."Table"
Parser should be able to handle quoted names properly. In this case the SQL should have been valid as is.
Confirmed that this does go right back to the Teiid parser. To confirm, the following test was included in
src/test/java/org/teiid/query/parser/TestParser.java
{code}
@Test
public void testQuotedSQLString() {
String sql = "SELECT * FROM \"My.Quoted.Table\""; //$NON-NLS-1$
String expected = "SELECT * FROM \"MY.QUOTED.TABLE\""; //$NON-NLS-1$
helpTest(sql, expected, null);
}
{code}
Test fails with a comparison error with the parser returning the SQL in item 3 above.
was:
1) Created source model with simple table named "My.Quoted.Table" (including quotes
2) Created simple virtual table and pasted: SELECT * FROM "My.Quoted.Table"
3) Parser returned a command resulting in the SQL: SELECT * FROM My.Quoted."Table"
Parser should be able to handle quoted names properly. In this case the SQL should have been valid as is.
> Adding source table with quoted name results in wrong generated SQL statement
> -----------------------------------------------------------------------------
>
> Key: TEIID-2993
> URL: https://issues.jboss.org/browse/TEIID-2993
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.7.2, 8.7
> Reporter: Paul Richardson
> Assignee: Steven Hawkins
> Fix For: 8.7.1, 8.8
>
>
> Cloned from TEIIDDES-2152:
> 1) Created source model with simple table named "My.Quoted.Table" (including quotes
> 2) Created simple virtual table and pasted: SELECT * FROM "My.Quoted.Table"
> 3) Parser returned a command resulting in the SQL: SELECT * FROM My.Quoted."Table"
> Parser should be able to handle quoted names properly. In this case the SQL should have been valid as is.
> Confirmed that this does go right back to the Teiid parser. To confirm, the following test was included in
> src/test/java/org/teiid/query/parser/TestParser.java
> {code}
> @Test
> public void testQuotedSQLString() {
> String sql = "SELECT * FROM \"My.Quoted.Table\""; //$NON-NLS-1$
> String expected = "SELECT * FROM \"MY.QUOTED.TABLE\""; //$NON-NLS-1$
> helpTest(sql, expected, null);
> }
> {code}
> Test fails with a comparison error with the parser returning the SQL in item 3 above.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months
[JBoss JIRA] (TEIID-2993) Adding source table with quoted name results in wrong generated SQL statement
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIID-2993?page=com.atlassian.jira.plugin... ]
Paul Richardson moved TEIIDDES-2202 to TEIID-2993:
--------------------------------------------------
Project: Teiid (was: Teiid Designer)
Key: TEIID-2993 (was: TEIIDDES-2202)
Affects Version/s: 8.7
7.7.2
(was: 8.5)
Assignee: Steven Hawkins (was: Paul Richardson)
Component/s: Query Engine
(was: Transformations)
Fix Version/s: 8.7.1
8.8
(was: 8.6)
(was: 8.3.4)
(was: 8.5.1)
> Adding source table with quoted name results in wrong generated SQL statement
> -----------------------------------------------------------------------------
>
> Key: TEIID-2993
> URL: https://issues.jboss.org/browse/TEIID-2993
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.7, 7.7.2
> Reporter: Paul Richardson
> Assignee: Steven Hawkins
> Fix For: 8.7.1, 8.8
>
>
> 1) Created source model with simple table named "My.Quoted.Table" (including quotes
> 2) Created simple virtual table and pasted: SELECT * FROM "My.Quoted.Table"
> 3) Parser returned a command resulting in the SQL: SELECT * FROM My.Quoted."Table"
> Parser should be able to handle quoted names properly. In this case the SQL should have been valid as is.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months
[JBoss JIRA] (TEIID-2989) Support odata batching
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2989?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2989:
---------------------------------------
> Do i have to make some configuration changes in Teiid for it to take the multiple entry ?
The above is not supported. Can you reference an OData specification about multi-entity creation?
I did also confirm that we do support OData batching, which could be used instead.
> Support odata batching
> ----------------------
>
> Key: TEIID-2989
> URL: https://issues.jboss.org/browse/TEIID-2989
> Project: Teiid
> Issue Type: Enhancement
> Components: OData
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.8
>
>
> We nearly have support for OData batching, but the ODataBatchingProvider is registered as a class and not as an instance. Otherwise it appears that a multipart/mixed post to an entity/$batch will allow for batching in OData4j.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months
[JBoss JIRA] (TEIID-2896) Add TEXTTABLE function capabilities to interpret fixed width data file content that is shorter than the defined line length
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIID-2896?page=com.atlassian.jira.plugin... ]
Barry LaFond commented on TEIID-2896:
-------------------------------------
The Flat File Importer feature was implemented with both character delimited and fixed width format options.
See: http://docs.jboss.org/teiid/designer/8.4/user-guide/en-US/html/importers-...
> Add TEXTTABLE function capabilities to interpret fixed width data file content that is shorter than the defined line length
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIID-2896
> URL: https://issues.jboss.org/browse/TEIID-2896
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Fix For: 8.7
>
> Attachments: sample, TEIID-2896.patch
>
>
> Current behavior is that data lines too short to fit a fixed width data interpretation produces an error such as "Error: Text parse error: Fixed width line width 35 is smaller than the expected 60 on text line 1 in file:/tmp/file.csv.". The customer's use case is interpreting data files from another application which bundles multiple types of data along with additional descriptive info/metadata about the data contained within the file. As the error is thrown if any lines after the first interpreted line are shorter than the summed value of the fixed width columns, they are unable to query the file. The customer wishes for the ERROR to be suppressed and the query to return the data independent of whether it fits the fixed width criteria and potentially to be able to filter the data being retrieved.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months