The look up step does as advertised. Returns 1 row per query/ lookupYou may wish to use the database joinTo do what you are looking for. Sent from my Galaxy -------- Original message --------From: Jonathan Haehnel <[email protected]> Date: 15/3/23 8:21 pm (GMT+10:00) To: [email protected] Subject: Database lookup only returns one row
Dear Hop Team, I tested the Database lookup step with two different Databases (mysql&redshift). Let’s say there is one input row. The lookup column value from input relates to several rows in the lookup table. I would expect to get several rows out as a result but only get one. Am I doing something wrong or is this a bug (didn’t fine a ticket for it in githup)? I can work around this issue using Database join but its not so nice, having to write a query and I assume also not as effective. select account_key from dwh.dim_account where email_key = ? Kind Regards Jonathan Jonathan Haehnel Business Intelligence Engineer Travian Games GmbH | Wilhelm-Wagenfeld-Str. 22 | 80807 Munich | Germany Tel.: +49 / (0)89 / 324 915 144 [email protected] http://www.traviangames.com Registered office: Munich Commercial register number: HRB 173511 Managing Directors: Jörg Strathaus, Frederik Hammes VAT ID: DE246258085 This email and its attachments are strictly confidential and are intended solely for the attention of the person to whom it is addressed. If you are not the intended recipient of this email, please delete it including its attachments immediately and inform us accordingly.
