| [ETL] ETL and launch configuration [message #632065] |
Mon, 11 October 2010 08:35  |
Eclipse User |
|
|
|
Hi,
Several of my students (me too) have had problems executing ETL
transformations, because we didn't use the same name for the model in
the ETL file and the launch configuration. E.g. you may think the name
in the ETL file (the part before the ! in type names, e.g.
football!Match) is the simple name of the package, while the name in the
launch configuration is the base name of the input file.
One way of helping the user, is to mention the model name in the launch
configuration in the error message, when the type name cannot be resolved.
Hallvard
|
|
|
|
|
| Re: [ETL] ETL and launch configuration [message #632110 is a reply to message #632106] |
Mon, 11 October 2010 11:24  |
| Eclipse User |
|
|
|
That's a great idea! We could definitely analyse the source of the ETL
transformation (or of any other Epsilon program for that reason) to find
out if there are references to undefined model element types.
Cheers,
Dimitris
Steffen Zschaler wrote:
> Couldn't you even do a validation of the launch configuration?
>
> Steffen
>
> On 11/10/2010 13:42, Dimitris Kolovos wrote:
>> Many thanks for the tip! Would you mind creating a bug report for this
>> so that we don't forget to implement this for the next release?
>>
>> Cheers,
>> Dimitris
>>
>> Hallvard Trætteberg wrote:
>>> Hi,
>>>
>>> Several of my students (me too) have had problems executing ETL
>>> transformations, because we didn't use the same name for the model in
>>> the ETL file and the launch configuration. E.g. you may think the
>>> name in the ETL file (the part before the ! in type names, e.g.
>>> football!Match) is the simple name of the package, while the name in
>>> the launch configuration is the base name of the input file.
>>>
>>> One way of helping the user, is to mention the model name in the
>>> launch configuration in the error message, when the type name cannot
>>> be resolved.
>>>
>>> Hallvard
|
|
|
| Re: [ETL] ETL and launch configuration [message #632279 is a reply to message #632110] |
Tue, 12 October 2010 07:53 |
| Eclipse User |
|
|
|
Dimitris,
Here's the request: https://bugs.eclipse.org/bugs/show_bug.cgi?id=327547
I've have suggested several ways of improving the situation, including
Steffen's.
Hallvard
On 11.10.10 17.24, Dimitris Kolovos wrote:
> That's a great idea! We could definitely analyse the source of the ETL
> transformation (or of any other Epsilon program for that reason) to find
> out if there are references to undefined model element types.
>
> Cheers,
> Dimitris
>
> Steffen Zschaler wrote:
>> Couldn't you even do a validation of the launch configuration?
>>
>> Steffen
>>
>> On 11/10/2010 13:42, Dimitris Kolovos wrote:
>>> Many thanks for the tip! Would you mind creating a bug report for
>>> this so that we don't forget to implement this for the next release?
>>>
>>> Cheers,
>>> Dimitris
>>>
>>> Hallvard Trætteberg wrote:
>>>> Hi,
>>>>
>>>> Several of my students (me too) have had problems executing ETL
>>>> transformations, because we didn't use the same name for the model
>>>> in the ETL file and the launch configuration. E.g. you may think the
>>>> name in the ETL file (the part before the ! in type names, e.g.
>>>> football!Match) is the simple name of the package, while the name in
>>>> the launch configuration is the base name of the input file.
>>>>
>>>> One way of helping the user, is to mention the model name in the
>>>> launch configuration in the error message, when the type name cannot
>>>> be resolved.
>>>>
>>>> Hallvard
|
|
|
Powered by
FUDForum. Page generated in 0.05037 seconds
Home