Hello,
We have a graph which includes a Reformat transformer. The Reformat is using a Database Lookup. I want to try some slightly different SQL
for the lookup. Rather than mess up the existing lookup, I created a new Database Lookup. Same Metadata, same connection, slightly different SQL which I have tested outside of clover. Selecting the same column names to match the metadata. In the Reformat transformer, I have commented out the original line of code and added a line which is identical except that it calls the new Database Lookup. The graph fails with the following error:
Error occurred in nested transformation: ERROR caused by:
Message: Transform failed! caused by: java.lang.IllegalStateException: Looking up has been never performed. Call seek method first
Hi,
I’ll also mention that my Clover ETL designer is acting funny when I try to work with these lookups.
For example:
- Open one of the lookups to review the query. Close
- Open the other lookup, click the Edit button
- The “Extracting” window pops up and just hangs. No matter how long I wait…it just hangs.
If I run the graph, I get the error and then I can’t even edit the lookup. I double click it and nothing happens. I need to close Clover ETL designer completely. In one case I could not even close. I had to kill clover from the task manager. What is going on?
please provide us with additional information.
- What’s the version of your Clover Designer (is it a 3.0 like you were using before)?
- Can you provide us both with your graph and the loookups?
Marek,
Thank you. Yes we are running 3.0.0. Is there some way I can send you the graph outside of the forum? This graph is one piece of a much bigger graph. It was created to isolate the sql we need to change.
I tried to reproduce your problems, but not succeed. You mentioned that you are trying to use “slightly different SQL”. Can you send me original and altered SQLs?
2 SQL queries you send are not really similar - the problematic one uses nested SQL. We are aware that older versions had issue with complex queries. However I am not able to reproduce your problem.
Workaround: What about replace “Database lookup table” by plain one initialized by you own?
I eventually got this working. It turns out that I had a dumb mistake in my code. I had changed the lookup .get call but neglected to change the .next call. So the .get was calling new lookup and .next was calling old lookup. Like I said…dumb. Anyway, thanks for your help, sorry for the trouble.