Making package BigQuery compatible

[DylanBaker]

A handful of changes in here to make the package BigQuery compatible:

• Adds a nested_field macro which formats columns correctly, depending on the warehouse it is using. (This change has only been pushed for the Stitch data, which was the source it was being tested on.)
• Add a stitch_base-table macro, which de-dupes Stitch data on BigQuery
• Changes concat to dbt_utils.concat macro for cross-db support.

I think the two new macros could probably move to https://github.com/fishtown-analytics/stitch-utils. We implemented specifically for this repo. Thought it might be easier to first push this change and then discuss the broader implications for the stitch-utils package after. Happy to discuss!

[DylanBaker]

@axelazaid @jtcohen6 Thought you two might be the best two to discuss with?

[jtcohen6]

@DylanBaker I'd be very open to bringing nested_data and stitch_base_table into stitch-utils! (I've previously thought about adding something along the lines of the latter, so very happy to see it here.) Happy to work on this before, after, or alongside the current PR :)

[DylanBaker]

@jtcohen6 I think my preference would be to do it in the following order (in part because I think it's easiest and in part because I'm most interested in getting it into facebook-ads quickest):

• work on this here and merge into facebook-ads
• bring the necessary logic into the stitch-utils package
• change the facebook-ads package to use the logic from stitch-utils

Does that sound good to you?

[Qashraf]

Hey @jtcohen6 , Not sure what the update with this is but like I mentioned @DylanBaker I used this branch and it worked for my needs. It seems like there's a conflict but that could probably be cleaned up with potentially an additional bigquery variable? Let me know if there's anything I can do to help get this PR cleaned up and added to to the package for everyone to use

[jtcohen6]

Everything in this PR looks reasonable. I'll be honest, it's been some time since I last used this package, so it's good to hear that it met your needs @Qashraf.

@DylanBaker If you get a chance to fix the merge conflict, I think we could merge this and cut a new minor release of the package. It doesn't seem like there are any breaking changes, but it's been a long time since the last patch release.

[jtcohen6]

I could see wanting this to be

Suggested change

	(select *
	(select * except (is_last_stitch_record)

Totally up to you on that one.

[clrcrl]

Closing since it's stale