Problem with extended property in static VDB while retrieving

[rajni.kumari14]

I have a static vdb which has some extended property(added by using mxd file) at  column level on View model and not on Source model.

eg:Column 'password' has an extended property 'isSecret'.

when I see the properties of the static vdb through SQuirrel Client, the extended property is displayed in the format given below:

     {'mxd Namespace URI'}Extension Property Name

in my case:

     {'mxd Namespace URI'} isSecret.

1) Why does the property have braces in extension property view ?

2) Is there a way to eliminate the braces and have it as follows:

     modelName.propertyName.

[rareddy]

Rajani,

The {'mxd Namespace URI'} is the namespace such that if there are two different properties with same name they do not conflict. No, you can not remove them.

However, I am surprised how you were able to view these properties in the SquirreL client? Can you pls explain?

BTW, unless you are doing some metadata data driven analysis, an extension property on view model to only useful to a Teiid internal processing. On source model, it is useful when you are writing a custom translator and would like to send additional metadata.

Thanks

Ramesh..

[shawkins]

> No, you can not remove them.

Designer is mimicing XML qualification as Ramesh says to avoid conflicting property keys.  When you need to reference the property on the server side you will use the the fully qualified Clark notation form with the braces to lookup the property value.

> However, I am surprised how you were able to view these properties in the SquirreL client? Can you pls explain?

They are visible in the system properties table.

> Is there a way to eliminate the braces and have it as follows: modelName.propertyName.

Designer ships the metadata to Teiid in the fully qualified form and does not offer an alternative scheme.  You are correct that having the properties act effectively as schema entries (or defined via a property table) is a more db centric approach.  However for Designer tracking and since Designer does not provide Teiid with the mdx metadata about the properties it's simplier to maintain the notion of properties as an external concept. 

Also, at this point the Teiid server does not require the use of a particular extension metadata key format.  If you want need a different extension key name, then consider exporting your static vdb metadata as DDL and modifying the OPTIONS clause extensions as desired.

[anilallewar]

Ok, we are able to see the custom properties in modelName.propertyName in our dynamic VDBs because we add it in that format through the translator.

But for static VDBs we will see the custom properties in the {modeName}propertyName format as that is how it is provided by the Teiid designer.