Translator Deployment in Teiid Jopr Plugin
by Ted Jones
There are two ways to create/deploy resources in Jopr:
1.) Via configuration - where the user enters the configuration values need to create and deploy a resource
2.) As a standalone resource file - think of war or vdb deployment here. The resource archive or file already exists and can be deployed via Jopr.
Any thoughts on which way we should go regarding Translators? If we go with 2, there will be a dependency on the Designer to actually create the Translator resource. If we go with 1, there will be no way to deploy an existing Translator through Jopr (other than manually). There *may* be a way to implement this as a Jopr operation from the Teiid runtime resource but it seems clunky to me to do it this way.
I am pursuing 1 for now due to the Designer dependency, but thought it would be good to air this out in the mailing lists as well in case there is some consideration I have overlooked.
Thanks,
Ted
13 years, 11 months
Re: [teiid-designer-dev] Translator Deployment in Teiid Jopr Plugin
by John Doyle
+1, right direction to take for now.
----- "Ted Jones" <tejones(a)redhat.com> wrote:
> There are two ways to create/deploy resources in Jopr:
>
> 1.) Via configuration - where the user enters the configuration values
> need to create and deploy a resource
>
> 2.) As a standalone resource file - think of war or vdb deployment
> here. The resource archive or file already exists and can be deployed
> via Jopr.
>
> Any thoughts on which way we should go regarding Translators? If we go
> with 2, there will be a dependency on the Designer to actually create
> the Translator resource. If we go with 1, there will be no way to
> deploy an existing Translator through Jopr (other than manually).
> There *may* be a way to implement this as a Jopr operation from the
> Teiid runtime resource but it seems clunky to me to do it this way.
>
> I am pursuing 1 for now due to the Designer dependency, but thought it
> would be good to air this out in the mailing lists as well in case
> there is some consideration I have overlooked.
>
> Thanks,
> Ted
> _______________________________________________
> teiid-designer-dev mailing list
> teiid-designer-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/teiid-designer-dev
13 years, 11 months
sql/xml functions
by Steven Hawkins
See https://jira.jboss.org/jira/browse/TEIID-171. With the next milestone there will be new SQL/XML functions. The impact to Designer should be limited, and will mostly be in the DisplayNode logic. The is because the xmlelement function does not have standard function syntax. And there are also the xmlattributes and xmlforest functions, that are actually implemented with a new expression type. You can see the formal definition of these functions in the SQL2003 spec. Let me know who to follow up to get support into Designer.
Steve
13 years, 11 months
