[JBoss JIRA] (TEIIDDES-3040) Source function in a virtual view, it expects an Object type as the result
by Colin Mondesir (JIRA)
Colin Mondesir created TEIIDDES-3040:
----------------------------------------
Summary: Source function in a virtual view, it expects an Object type as the result
Key: TEIIDDES-3040
URL: https://issues.jboss.org/browse/TEIIDDES-3040
Project: Teiid Designer
Issue Type: Bug
Affects Versions: 10.0.2
Reporter: Colin Mondesir
On a physical model, I have created a Source Function INSTR with the following parameters:
IN char1 string
IN char2 string
RETURN result Integer
When I use this source function in a virtual view, it expects an Object type as the result of this function. No way to force with an Integer type. So I create an Object column to store this result. But then I create a VDB and I want to deploy it, it tells me that it expects a Integer result and not an Object.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years
[JBoss JIRA] (TEIIDDES-3028) Add "LoadNumber" column to Materialized View cache tables
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3028?page=com.atlassian.jira.plu... ]
Van Halbert commented on TEIIDDES-3028:
---------------------------------------
For The JDG materialize use case needs to be tested with this, so that the pojo that is created will contain the loadnumber attribute. And for this use case, will also need to do the following:
- do not fill in the following:
MATVIEW_BEFORE_LOAD_SCRIPT
MATVIEW_AFTER_LOAD_SCRIPT
MATERIALIZED_STAGE_TABLE
- do not create the "Staging" table
We need to fully discuss how this will all roll out and implications to the original feature.
> Add "LoadNumber" column to Materialized View cache tables
> ---------------------------------------------------------
>
> Key: TEIIDDES-3028
> URL: https://issues.jboss.org/browse/TEIIDDES-3028
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Modeling
> Reporter: Ramesh Reddy
> Priority: Blocker
> Fix For: 11.2
>
>
> Based on TEIID-4628, to work with eager updates on materiliazed view, a materialized view's cached table MUST contain an additional column called "LoadNumber" along with rest of view columns. This column is used track the and update the cache contents according to the
> {code}
> SYSADMIN.updatematView
> {code}
> procedure. The relevant document can be found at https://teiid.gitbooks.io/documents/content/caching/External_Materializat...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years
[JBoss JIRA] (TEIIDDES-2185) Update the States Web Service Example
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2185?page=com.atlassian.jira.plu... ]
Matus Makovy resolved TEIIDDES-2185.
------------------------------------
Resolution: Done
attached example is OK,
[~tejones]
Will you please replace the package on jboss.org with the attached one?
I will mark this as Resolved and once there will be new zip uploaded to jboss.org I will close this.
> Update the States Web Service Example
> -------------------------------------
>
> Key: TEIIDDES-2185
> URL: https://issues.jboss.org/browse/TEIIDDES-2185
> Project: Teiid Designer
> Issue Type: Task
> Components: Patch Release, Web Services Support
> Affects Versions: 8.3.2
> Reporter: Ted Jones
> Assignee: Ted Jones
> Fix For: 11.0.1
>
> Attachments: StateServiceExampleFull.zip
>
>
> The States Web Service example is missing the "stream" parameter in the invoke() procedure. Need to recreate to include this parameter.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years
[JBoss JIRA] (TEIIDDES-2493) Check for spaces in the parent directory Flat File connection importer
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2493?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2493:
----------------------------------------
I think what we've arrived at is that because the server and Tooling can be running on different OS's then the Tooling can't guarantee that the URL sent to the server as a property will actually work on the server. So our options/notes are:
1) Add some validation logic to Designer to validate the URL on entry and warn the user that any "Spaces" in the URL or path may render the URL useless on some OS's. Also add logic to validate the URL and warn them during Create Data Source actions.
2) In reality, the URL is used on the Server side and errors out on some OS's because of the invalid format. A user can hand-edit the standalone.xml config file and break it anyway. Unless the Teiid Runtime is using this URL and creating it's on connections, there's not much they can do either to prevent the error from occurring by massaging the URL to make it valid based on OS.
> Check for spaces in the parent directory Flat File connection importer
> ----------------------------------------------------------------------
>
> Key: TEIIDDES-2493
> URL: https://issues.jboss.org/browse/TEIIDDES-2493
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, Patch Release
> Reporter: Ramesh Reddy
> Assignee: Mark Drilling
> Fix For: 11.1
>
>
> Add a check to make sure there are no spaces in the ParentDirectory or root directory path when Flat File Connection Profile is chosen.
> ====================
> The problem is manifested on the server when attempting to query the datasource. On datasource creation, the resource adapter is written to the standalone.xml like this.
> {code:java}
> <config-property name="ParentDirectory">
> /home/mdrilling/My Dir/data
> </config-property>
> {code}
> The embedded space in the ParentDirectory property value is problematic.
> Need to determine whether to (1) disallow a path with spaces or (2) allow it, replacing the space with the appropriate control code ie {code:java} {code} - like this
> {code:java}
> <config-property name="ParentDirectory">
> /home/mdrilling/My Dir/data
> </config-property>
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years
[JBoss JIRA] (TEIIDDES-3038) Designer is not aware of the system schema "SYSADMIN"
by Tom Johnston (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3038?page=com.atlassian.jira.plu... ]
Tom Johnston commented on TEIIDDES-3038:
----------------------------------------
I just tested JBDS Version: 10.2.0.GA
with: Teiid Designer 11.0.0.Final-v20170124-2055-B4134 org.teiid.designer.feature.feature.group JBoss by Red Hat
This HAS the SYSADMIN Schema but NOT the Usage table that my query references.
> Designer is not aware of the system schema "SYSADMIN"
> -----------------------------------------------------
>
> Key: TEIIDDES-3038
> URL: https://issues.jboss.org/browse/TEIIDDES-3038
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.0.2
> Environment: Teiid Designer 10.0.2.Final-v20161108-1636-B72 org.teiid.designer.feature.feature.group JBoss by Red Hat
> Reporter: Tom Johnston
> Assignee: Barry LaFond
>
> SELECT
> a.*, b.TablesUsed, b.isPhysical
> FROM
> (SELECT DISTINCT ((x.SchemaName || '.') || x.Name) AS FQN_Object, ((x.Uses_schemaName || '.') || x.Uses_Name) AS tablesUsed, y.isPhysical FROM SYSADMIN.Usage AS x, SYS.Schemas AS y WHERE (y.name = x.SchemaName) AND (x.schemaName NOT IN ('SYS', 'SYSADMIN')) ORDER BY ((x.SchemaName || '.') || x.Name)) AS a LEFT OUTER JOIN (SELECT DISTINCT ((x.SchemaName || '.') || x.Name) AS FQN_Object, ((x.Uses_schemaName || '.') || x.Uses_Name) AS tablesUsed, y.isPhysical FROM SYSADMIN.Usage AS x, SYS.Schemas AS y WHERE (y.Name = x.SchemaName) AND (x.schemaName NOT IN ('SYS', 'SYSADMIN')) ORDER BY ((x.SchemaName || '.') || x.Name)) AS B ON a.TablesUsed = b.FQN_Object
> Results in
> ERROR: Group does not exist: SYSADMIN.Usage AS x
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years
[JBoss JIRA] (TEIIDDES-3036) Create POJO doesn't generate anything when one of the columns has a column type biginteger
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3036?page=com.atlassian.jira.plu... ]
Van Halbert commented on TEIIDDES-3036:
---------------------------------------
Need to consider in making the process proactive, in that it doesn't allow the creation of a pojo when certain data types are being used. And provide a message indicating options (like, creating the marshaller or changing the data type to string, etc.)
> Create POJO doesn't generate anything when one of the columns has a column type biginteger
> ------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-3036
> URL: https://issues.jboss.org/browse/TEIIDDES-3036
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.0.2
> Environment: JBoss Developer Studio 9.1.0 with Teiid Designer 10.0.2 installed
> Reporter: Cojan van Ballegooijen
> Attachments: Screen Shot 2017-02-09 at 12.02.56.png
>
>
> Creating a POJO from a source model table doesn't generate the classes and module zip file when one of the columns has a datatype biginteger.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years
[JBoss JIRA] (TEIIDDES-3038) Designer is not aware of the system schema "SYSADMIN"
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3038?page=com.atlassian.jira.plu... ]
Matus Makovy updated TEIIDDES-3038:
-----------------------------------
Affects Version/s: 10.0.2
> Designer is not aware of the system schema "SYSADMIN"
> -----------------------------------------------------
>
> Key: TEIIDDES-3038
> URL: https://issues.jboss.org/browse/TEIIDDES-3038
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.0.2
> Environment: Teiid Designer 10.0.2.Final-v20161108-1636-B72 org.teiid.designer.feature.feature.group JBoss by Red Hat
> Reporter: Tom Johnston
> Assignee: Barry LaFond
>
> SELECT
> a.*, b.TablesUsed, b.isPhysical
> FROM
> (SELECT DISTINCT ((x.SchemaName || '.') || x.Name) AS FQN_Object, ((x.Uses_schemaName || '.') || x.Uses_Name) AS tablesUsed, y.isPhysical FROM SYSADMIN.Usage AS x, SYS.Schemas AS y WHERE (y.name = x.SchemaName) AND (x.schemaName NOT IN ('SYS', 'SYSADMIN')) ORDER BY ((x.SchemaName || '.') || x.Name)) AS a LEFT OUTER JOIN (SELECT DISTINCT ((x.SchemaName || '.') || x.Name) AS FQN_Object, ((x.Uses_schemaName || '.') || x.Uses_Name) AS tablesUsed, y.isPhysical FROM SYSADMIN.Usage AS x, SYS.Schemas AS y WHERE (y.Name = x.SchemaName) AND (x.schemaName NOT IN ('SYS', 'SYSADMIN')) ORDER BY ((x.SchemaName || '.') || x.Name)) AS B ON a.TablesUsed = b.FQN_Object
> Results in
> ERROR: Group does not exist: SYSADMIN.Usage AS x
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years