March 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2715) Extension metadata is not visible when queried through OData

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2715?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2715: ------------------------------------- On V4 there support for annotations in metadata, but the support is generally not available yet in frameworks > Extension metadata is not visible when queried through OData > ------------------------------------------------------------ > > Key: TEIID-2715 > URL: https://issues.jboss.org/browse/TEIID-2715 > Project: Teiid > Issue Type: Enhancement > Components: Server > Affects Versions: 8.6 > Environment: Windows 7 > Reporter: Alex Khvatov > > x`Hi, > I used Teiid Designer and just plain XML editor (because Teiid Designer would constantly complain) I created Model Extension Definition file which I was able to successfully register. My definition was showing up in Model Extension Registry view. I deployed my virtual database and tried accessing columns and tables via Odata: > http://localhost:8080/odata/MCR_VDB/Tables?$format=json > http://localhost:8080/odata/MCR_VDB/Columns?$format=json > Both documents returned did not contain any extra metadata I defined. > HELP! > Thanks. > Alex -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2715) Extension metadata is not visible when queried through OData

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2715?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2715: --------------------------------------- Is there anything in the OData metadata that allows for arbitrary properties? If not a system procedure would be fine. > Extension metadata is not visible when queried through OData > ------------------------------------------------------------ > > Key: TEIID-2715 > URL: https://issues.jboss.org/browse/TEIID-2715 > Project: Teiid > Issue Type: Enhancement > Components: Server > Affects Versions: 8.6 > Environment: Windows 7 > Reporter: Alex Khvatov > > x`Hi, > I used Teiid Designer and just plain XML editor (because Teiid Designer would constantly complain) I created Model Extension Definition file which I was able to successfully register. My definition was showing up in Model Extension Registry view. I deployed my virtual database and tried accessing columns and tables via Odata: > http://localhost:8080/odata/MCR_VDB/Tables?$format=json > http://localhost:8080/odata/MCR_VDB/Columns?$format=json > Both documents returned did not contain any extra metadata I defined. > HELP! > Thanks. > Alex -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2715) Extension metadata is not visible when queried through OData

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2715?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2715: ------------------------------------- May be we can add a virtual procedure for this? getProperties(type => [TABLE|COLUMN|PROCEDURE|FUNCTION], ...) > Extension metadata is not visible when queried through OData > ------------------------------------------------------------ > > Key: TEIID-2715 > URL: https://issues.jboss.org/browse/TEIID-2715 > Project: Teiid > Issue Type: Enhancement > Components: Server > Affects Versions: 8.6 > Environment: Windows 7 > Reporter: Alex Khvatov > > x`Hi, > I used Teiid Designer and just plain XML editor (because Teiid Designer would constantly complain) I created Model Extension Definition file which I was able to successfully register. My definition was showing up in Model Extension Registry view. I deployed my virtual database and tried accessing columns and tables via Odata: > http://localhost:8080/odata/MCR_VDB/Tables?$format=json > http://localhost:8080/odata/MCR_VDB/Columns?$format=json > Both documents returned did not contain any extra metadata I defined. > HELP! > Thanks. > Alex -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2715) Extension metadata is not visible when queried through OData

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2715?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-2715: -------------------------------- Summary: Extension metadata is not visible when queried through OData (was: Created and registered MXD, extra metadata is not visible when queried.) > Extension metadata is not visible when queried through OData > ------------------------------------------------------------ > > Key: TEIID-2715 > URL: https://issues.jboss.org/browse/TEIID-2715 > Project: Teiid > Issue Type: Enhancement > Components: Server > Affects Versions: 8.6 > Environment: Windows 7 > Reporter: Alex Khvatov > > x`Hi, > I used Teiid Designer and just plain XML editor (because Teiid Designer would constantly complain) I created Model Extension Definition file which I was able to successfully register. My definition was showing up in Model Extension Registry view. I deployed my virtual database and tried accessing columns and tables via Odata: > http://localhost:8080/odata/MCR_VDB/Tables?$format=json > http://localhost:8080/odata/MCR_VDB/Columns?$format=json > Both documents returned did not contain any extra metadata I defined. > HELP! > Thanks. > Alex -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3371) Upgrade Teiid with EAP 6.4 Alpha

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3371?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-3371: -------------------------------- Fix Version/s: 8.11 > Upgrade Teiid with EAP 6.4 Alpha > -------------------------------- > > Key: TEIID-3371 > URL: https://issues.jboss.org/browse/TEIID-3371 > Project: Teiid > Issue Type: Enhancement > Components: Build/Kits > Affects Versions: 8.11 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Fix For: 8.11 > > Attachments: diff.txt, status.txt > > > Upgrade all the Teiid projects to be built based on EAP 6.4 Alpha. Currently, this would align with jboss-integration-platform-bom 6.0.0.CR25 and EAP Alpha version 7.5.0.Final-redhat-17. Note, 7.5.0.Final-redhat-17 is the version in the EAP kit, but only CR25 bom is available. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3397) invokeHttp can only be streaming

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3397?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3397. ----------------------------------- Resolution: Rejected I should have spent a little longer looking at this. The datasource that is returned is fronted by a save on read input stream so that it can be reused. > invokeHttp can only be streaming > -------------------------------- > > Key: TEIID-3397 > URL: https://issues.jboss.org/browse/TEIID-3397 > Project: Teiid > Issue Type: Quality Risk > Components: Misc. Connectors > Affects Versions: 8.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > > With the switch to use webclient, the invokeHttp method can only be streaming. We should note that in the docs or provide a non streaming option. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3397) invokeHttp can only be streaming

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3397?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3397: ---------------------------------- Issue Type: Quality Risk (was: Feature Request) > invokeHttp can only be streaming > -------------------------------- > > Key: TEIID-3397 > URL: https://issues.jboss.org/browse/TEIID-3397 > Project: Teiid > Issue Type: Quality Risk > Components: Misc. Connectors > Affects Versions: 8.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > > With the switch to use webclient, the invokeHttp method can only be streaming. We should note that in the docs or provide a non streaming option. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3397) invokeHttp can only be streaming

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3397: ------------------------------------- Summary: invokeHttp can only be streaming Key: TEIID-3397 URL: https://issues.jboss.org/browse/TEIID-3397 Project: Teiid Issue Type: Feature Request Components: Misc. Connectors Affects Versions: 8.4 Reporter: Steven Hawkins Assignee: Steven Hawkins With the switch to use webclient, the invokeHttp method can only be streaming. We should note that in the docs or provide a non streaming option. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3274) Change archetypes to create independent projects

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3274?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3274: ------------------------------------------------ Filip Elias <felias(a)redhat.com> changed the Status of [bug 1178658|https://bugzilla.redhat.com/show_bug.cgi?id=1178658] from ASSIGNED to VERIFIED > Change archetypes to create independent projects > ------------------------------------------------ > > Key: TEIID-3274 > URL: https://issues.jboss.org/browse/TEIID-3274 > Project: Teiid > Issue Type: Enhancement > Components: Tools > Affects Versions: 8.7.1 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.7.1 > > > The current archetypes were developed with the mindset of generating projects that are part of the Teiid build. However, they need to be changed so that they are generating projects that are independent, that can stand on their own without requiring Teiid jar's. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3391) Double value is truncated in Where clause

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3391?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3391. ----------------------------------- Resolution: Rejected Marking as rejected from the Teiid side as this is not reproducible with a dynamic vdb using H2 double precision types. If the metadata was obtained through Teiid designer, please reopen and move this issue there as they may be mistakenly mapping the H2 float source type to the Teiid runtime float type rather than to double. > Double value is truncated in Where clause > ----------------------------------------- > > Key: TEIID-3391 > URL: https://issues.jboss.org/browse/TEIID-3391 > Project: Teiid > Issue Type: Feature Request > Reporter: Mark Tawk > Assignee: Steven Hawkins > Priority: Blocker > > I'm using Teiid 8.10.0 Final over H2 Database. > I have an H2 table containing a field of Type Double. > When i add a where condition over this field with a double value, this value is truncated by Teiid and the query returns no records. > You find below the query executed with Teiid and the execution plan: > select "Locations"."Sheet0_EPr_090315_Lat" as "LAT_MapCalculatedField","Locations"."Sheet0_EPr_090315_Long" as "LNG_MapCalculatedField","Locations"."Sheet0_EPr_090315_SDView_INC" as "Locations_Sheet0_EPr_090315_1",COUNT( distinct "IM123View"."SDView_INCIDENTSM1_INCIDENT_") as "IM123View_SDView_INCIDENTSM1" from "implifyBusinessModel"."IM123View" "IM123View" LEFT JOIN "implifyBusinessModel"."Locations" "Locations" ON "IM123View"."SDView_INCIDENTSM1_LOCATION_" = "Locations"."Sheet0_EPr_090315_SDView_INC" > where ("Locations"."Sheet0_EPr_090315_Lat" IN (31.953582763671875) ) group by "Locations"."Sheet0_EPr_090315_Lat","Locations"."Sheet0_EPr_090315_Long","Locations"."Sheet0_EPr_090315_SDView_INC" > -----Teiid Show Plan ---- > <?xml version='1.0' encoding='UTF-8'?><node name="AccessNode"><property name="Relational Node ID"><value>1</value></property><property name="Output Columns"><value>LAT_MapCalculatedField (float)</value><value>LNG_MapCalculatedField (float)</value><value>Locations_Sheet0_EPr_090315_1 (string)</value><value>IM123View_SDView_INCIDENTSM1 (integer)</value></property><property name="Statistics"><value>Node Output Rows: 0</value><value>Node Next Batch Process Time: 0</value><value>Node Cumulative Next Batch Process Time: 0</value><value>Node Cumulative Process Time: 16</value><value>Node Next Batch Calls: 2</value><value>Node Blocks: 1</value></property><property name="Cost Estimates"><value>Estimated Node Cardinality: -1.0</value></property><property name="Query"><value> > SELECT g_1.Sheet0_EPr_090315_Lat, g_1.Sheet0_EPr_090315_Long, g_1.Sheet0_EPr_090315_SDView_INC, COUNT(DISTINCT g_0.SDView_INCIDENTSM1_INCIDENT_) > FROM implify_viewModel.implify_view.IM123View AS g_0, implify_viewModel.implify_view.Locations AS g_1 WHERE (g_0.SDView_INCIDENTSM1_LOCATION_ = g_1.Sheet0_EPr_090315_SDView_INC) AND (g_1.Sheet0_EPr_090315_Lat = 31.953583) GROUP BY g_1.Sheet0_EPr_090315_Lat, g_1.Sheet0_EPr_090315_Long, g_1.Sheet0_EPr_090315_SDView_INC</value></property><property name="Model Name"><value>implify_viewModel</value></property><property name="Data Bytes Sent"><value>0</value></property></node> -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2015