1 of 1 people found this helpful
> I am using Teiid Designer 11.1 (the latest) so I am wondering why I still see this error.
It is marked as resolved in 11.1.1
The expectation is that Designer will only add those columns for Teiid versions that support the extended functionality. The bug should only be observed when the columns are added by Designer, but the runtime does not support returning them.
If you use the metadata with just the two columns defined the server logic will understand that regardless of the version.
If you use a -vdb.xml that excludes defining the source model, you will either get the behavior you expect or a clearer error as the procedure metadata will be defined by the runtime.
> But my next question is: Why did the issue resolve by just removing the 3 getTextFiles() procedure result columns from just ONE of my source models, and not all 3 of them?
This is a runtime error, are you invoking all three?
I did not add those columns in Designer, they were added automatically when I imported my text file using getTextFiles() procedure. My Teiid Designer version is 11.1 and is compatible with Teiid 9.0 release, so that means that the Designer should have just added the columns specific to Teiid version (9.0)
When I look at download website, I see 11.1.0 is the final release. Where do I find the 11.1.1 Teiid Designer version?
To answer your next question, yes
My REST procedure invokes 3 other procedures that look at the 3 source models, so yes, I am using all 3 source models. Any ideas why I did not have to remove the columns for the other 2 models?
11.1.1 is not released yet.
I am not sure if you provide the DDL version of the VDB we can take a look. Unless your parent directory is different for each one, you technically only need one "file" based model. The reason it may be working is if model name prefix is not used like
Then they resolve to matching procedure.