Hi,
Iam trying to load a fact table. One of the transformation rule states that
I do a look up on two tables which are other than the "source" and pull out
field(SID) and load it in the fact table(without any lookup from the source).
For that I did a lookup on those two tables and pulled out a field and loaded into a
hash file and linked it with the transformer that is loading the fact table.But
the field(SID) is shown red in the transformer and giving me compilation errors.
can anybody suggest a way to tackle this problem.
Thanx.
Compilation errors
Moderators: chulett, rschirm, roy
Re: Compilation errors
There is no lookup with the main source table thats the problem.sdfasih wrote:Hi,
Iam trying to load a fact table. One of the transformation rule states that
I do a look up on two tables which are other than the "source" and pull out
field(SID) and load it in the fact table(without any lookup from the source).
For that I did a lookup on those two tables and pulled out a field and loaded into a
hash file and linked it with the transformer that is loading the fact table.But
the field(SID) is shown red in the transformer and giving me compilation errors.
can anybody suggest a way to tackle this problem.
Thanx.
-
- Charter Member
- Posts: 560
- Joined: Wed Jul 13, 2005 5:36 am
- Location: Ohio
-
- Participant
- Posts: 73
- Joined: Wed Jun 28, 2006 3:27 pm
- Location: NJ
You said without doing lookup with the source ???
And why you need to build a hashed file if the table itself can be used for the lookup.. More over I guess you are doing the same thing by building the hashed file and then using it as look up ..
So Correct me if i m wrong :
your job is like -
SourceTable->Transformer->OutputTable
^ ^
| |
Table1 Table2
Table1 and Table2 are for lookups correct ??
If this is so no need to build the hashed file. Unless its a huge data. Or you can build it in other job and take the hashed file in your this job. Its coming red because you must have set the Primary key and not linked with the source.
Hope this if fine exp.
And why you need to build a hashed file if the table itself can be used for the lookup.. More over I guess you are doing the same thing by building the hashed file and then using it as look up ..
So Correct me if i m wrong :
your job is like -
SourceTable->Transformer->OutputTable
^ ^
| |
Table1 Table2
Table1 and Table2 are for lookups correct ??
If this is so no need to build the hashed file. Unless its a huge data. Or you can build it in other job and take the hashed file in your this job. Its coming red because you must have set the Primary key and not linked with the source.
Hope this if fine exp.
"Nobody is expert in Everything,
But Everybody is expert in Something."
But Everybody is expert in Something."
-
- Participant
- Posts: 73
- Joined: Wed Jun 28, 2006 3:27 pm
- Location: NJ