[teiid-issues] [JBoss JIRA] (TEIID-2715) Created and registered MXD, extra metadata is not visible when queried.

Steven Hawkins (JIRA) jira-events at lists.jboss.org
Thu Nov 21 09:11:06 EST 2013


     [ https://issues.jboss.org/browse/TEIID-2715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins updated TEIID-2715:
----------------------------------

                Issue Type: Enhancement  (was: Bug)
    Workaround Description: Create a view that contains the desired properties by joining against the properties table.
                Workaround: Workaround Exists


Switching to an enhancement as given the current structure of the system schema there isn't an inherent issue now that TEIID-2718 has been resolved. 

The general question here is about the usability of extension metadata from odata.  There isn't currently a good relationship between the properties table and all of the object type tables. 

The workaround is to have the user create a view to denormalize the properties how ever they see fit.

As for built-in work, to expose the extension properties a little more naturally we could add columns to the properties table so that it can be queried by something other than uid, or add navigatable relations like table_properties.  There may also be something in odata's metadata that will allow arbitrary properties - although I did not see that at first glance.
                
> Created and registered MXD, extra metadata is not visible when queried.
> -----------------------------------------------------------------------
>
>                 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
>            Assignee: Steven Hawkins
>
> 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 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


More information about the teiid-issues mailing list