January 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2824) Change translator-archetype to provide zip packaging of the module

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2824?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-2824: ------------------------------- Git Pull Request: https://github.com/teiid/teiid-tools/pull/7 > Change translator-archetype to provide zip packaging of the module > ------------------------------------------------------------------ > > Key: TEIID-2824 > URL: https://issues.jboss.org/browse/TEIID-2824 > Project: Teiid > Issue Type: Sub-task > Components: Tools > Affects Versions: 8.7 > Reporter: Van Halbert > Assignee: Van Halbert > > Change translator-archetype to provide zip packaging of the module -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2827) Can the teiid object associated with where the problem is found be added to the error message

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2827?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-2827: ------------------------------- Summary: Can the teiid object associated with where the problem is found be added to the error message (was: Not sure why Teiid is creating errors based on the database metadata) If the Teiid object, for which contains the statement that is invalid, could be identified in the Error message, that could assist in problem resolution. > Can the teiid object associated with where the problem is found be added to the error message > --------------------------------------------------------------------------------------------- > > Key: TEIID-2827 > URL: https://issues.jboss.org/browse/TEIID-2827 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > Attachments: createdb.sql, perf-vdb-postgres.xml > > > Using the attached dynamic vdb, against the database that was created using the attached DDL, produces the following errors: > ERROR: Element Perf.HISTORY."TIME" of history is neither nullable nor has a default value. A value must be specified in the insert. > ERROR: Element Perf.HISTORY.FILL of history is neither nullable nor has a default value. A value must be specified in the insert. > Because of these errors, the VDB isn't deployed. > Not sure why these are not just WARNINGS. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2828) ResteasyEnabler fails with OTHER model types

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2828: ------------------------------------- Summary: ResteasyEnabler fails with OTHER model types Key: TEIID-2828 URL: https://issues.jboss.org/browse/TEIID-2828 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 8.4 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.7 If a vdb contains OTHER type models (typically used for .xsd), then the schema lookup will produce a null and result in an NPE: java.lang.NullPointerException at org.teiid.jboss.rest.ResteasyEnabler.hasRestMetadata(ResteasyEnabler.java:146) [teiid-jboss-integration-8.4.1-redhat-2.jar:8.4.1-redhat-2] at org.teiid.jboss.rest.ResteasyEnabler.finishedDeployment(ResteasyEnabler.java:81) [teiid-jboss-integration-8.4.1-redhat-2.jar:8.4.1-redhat-2] at org.teiid.deployers.VDBRepository.notifyFinished(VDBRepository.java:351) [teiid-runtime-8.4.1-redhat-2.jar:8.4.1-redhat-2] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2815) Need to add the aggregate functions to list of supported functions, for Designer to expose for the user

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2815?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2815: --------------------------------------- After looking at it more, we'll have you guys take ownership of FunctionForm as it's just an adapter for FunctionMethod (the metadata api representation) and is not useful to Teiid. The change for this: - removes FunctionForm - add FunctionLibrary.getBuiltInAggregateFunctions(boolean includeAnaylitic) this will return a list of FunctionMethods representing the aggregate metadata. count\(*) and textagg are not in the list since their syntax is not well represented in our metadata. If it's ok, this will just return the most general form of some of the aggregates, for example object max(object) rather than an entry for each type. - changed the findFunctionForm method to hasFunctionMethod - changed the category method to getFunctionsInCategory which returns a list of FunctionMethods User defined aggregates are just exposed through the normal function logic on FunctionLibrary. The TODOs then are to create further adapt the logic in Teiid to use the FunctionMethod representation internally for all aggregates and not just user defined aggregates. We also need to a way to express count\(*) and at least internally standardize the syntax for textagg - which effectively relies upon a hidden function called textline that builds each line of the result. > Need to add the aggregate functions to list of supported functions, for Designer to expose for the user > ------------------------------------------------------------------------------------------------------- > > Key: TEIID-2815 > URL: https://issues.jboss.org/browse/TEIID-2815 > Project: Teiid > Issue Type: Enhancement > Components: Server > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > > Need to add to the list, of known supported functions, what are all the aggregate functions that are supported. This list is what Teiid Designer would expose to the user for modeling purposes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2827) Not sure why Teiid is creating errors based on the database metadata

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2827?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2827: --------------------------------------- To add a little bit more here, this check is primarily for virtual inserts but has always been in place regardless of the target. This may seem like somewhat selective of a check given that other things such as referential constraints we leave up to the source system. Beyond that consideration, what was the full extent of what you saw in the logs? If we are not at least associating the procedure name with the validation error, then that's an issue. > Not sure why Teiid is creating errors based on the database metadata > -------------------------------------------------------------------- > > Key: TEIID-2827 > URL: https://issues.jboss.org/browse/TEIID-2827 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > Attachments: createdb.sql, perf-vdb-postgres.xml > > > Using the attached dynamic vdb, against the database that was created using the attached DDL, produces the following errors: > ERROR: Element Perf.HISTORY."TIME" of history is neither nullable nor has a default value. A value must be specified in the insert. > ERROR: Element Perf.HISTORY.FILL of history is neither nullable nor has a default value. A value must be specified in the insert. > Because of these errors, the VDB isn't deployed. > Not sure why these are not just WARNINGS. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2827) Not sure why Teiid is creating errors based on the database metadata

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2827?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2827: --------------------------------------- Presumably the source does allow for those columns to be defaultable. It's just not reflected in the created external table statements you're showing here. When you change the column s to be null able then we know there is an appropriate default. > Not sure why Teiid is creating errors based on the database metadata > -------------------------------------------------------------------- > > Key: TEIID-2827 > URL: https://issues.jboss.org/browse/TEIID-2827 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > Attachments: createdb.sql, perf-vdb-postgres.xml > > > Using the attached dynamic vdb, against the database that was created using the attached DDL, produces the following errors: > ERROR: Element Perf.HISTORY."TIME" of history is neither nullable nor has a default value. A value must be specified in the insert. > ERROR: Element Perf.HISTORY.FILL of history is neither nullable nor has a default value. A value must be specified in the insert. > Because of these errors, the VDB isn't deployed. > Not sure why these are not just WARNINGS. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2827) Not sure why Teiid is creating errors based on the database metadata

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2827?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-2827: ------------------------------------ You're right. Interesting that this TPC-B test didn't notice this. > Not sure why Teiid is creating errors based on the database metadata > -------------------------------------------------------------------- > > Key: TEIID-2827 > URL: https://issues.jboss.org/browse/TEIID-2827 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > Attachments: createdb.sql, perf-vdb-postgres.xml > > > Using the attached dynamic vdb, against the database that was created using the attached DDL, produces the following errors: > ERROR: Element Perf.HISTORY."TIME" of history is neither nullable nor has a default value. A value must be specified in the insert. > ERROR: Element Perf.HISTORY.FILL of history is neither nullable nor has a default value. A value must be specified in the insert. > Because of these errors, the VDB isn't deployed. > Not sure why these are not just WARNINGS. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2827) Not sure why Teiid is creating errors based on the database metadata

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2827?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2827: --------------------------------------- You are inserting into a table with 6 columns but only providing 4 values. It is valid for us to complain about this as the missing columns are not nullable nor have a default. So I think your chief complaint here may be that there wasn't enough context to the error. > Not sure why Teiid is creating errors based on the database metadata > -------------------------------------------------------------------- > > Key: TEIID-2827 > URL: https://issues.jboss.org/browse/TEIID-2827 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > Attachments: createdb.sql, perf-vdb-postgres.xml > > > Using the attached dynamic vdb, against the database that was created using the attached DDL, produces the following errors: > ERROR: Element Perf.HISTORY."TIME" of history is neither nullable nor has a default value. A value must be specified in the insert. > ERROR: Element Perf.HISTORY.FILL of history is neither nullable nor has a default value. A value must be specified in the insert. > Because of these errors, the VDB isn't deployed. > Not sure why these are not just WARNINGS. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2827) Not sure why Teiid is creating errors based on the database metadata

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2827?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-2827: ------------------------------------ I got around the problem by altering the columns to make them nullable, but that shouldn't have had to be the solution. And its interesting that it only focused on these 2 columns, when there were other columns that are not nullable and do not provide a default value. > Not sure why Teiid is creating errors based on the database metadata > -------------------------------------------------------------------- > > Key: TEIID-2827 > URL: https://issues.jboss.org/browse/TEIID-2827 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > Attachments: createdb.sql, perf-vdb-postgres.xml > > > Using the attached dynamic vdb, against the database that was created using the attached DDL, produces the following errors: > ERROR: Element Perf.HISTORY."TIME" of history is neither nullable nor has a default value. A value must be specified in the insert. > ERROR: Element Perf.HISTORY.FILL of history is neither nullable nor has a default value. A value must be specified in the insert. > Because of these errors, the VDB isn't deployed. > Not sure why these are not just WARNINGS. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2827) Not sure why Teiid is creating errors based on the database metadata

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2827?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-2827: ------------------------------- Attachment: createdb.sql perf-vdb-postgres.xml > Not sure why Teiid is creating errors based on the database metadata > -------------------------------------------------------------------- > > Key: TEIID-2827 > URL: https://issues.jboss.org/browse/TEIID-2827 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > Attachments: createdb.sql, perf-vdb-postgres.xml > > > Using the attached dynamic vdb, against the database that was created using the attached DDL, produces the following errors: > ERROR: Element Perf.HISTORY."TIME" of history is neither nullable nor has a default value. A value must be specified in the insert. > ERROR: Element Perf.HISTORY.FILL of history is neither nullable nor has a default value. A value must be specified in the insert. > Because of these errors, the VDB isn't deployed. > Not sure why these are not just WARNINGS. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2014