[10:38:37] <tanny411>	 @dcausse I wrote the schemas for all the tables related to subgraph analysis. Wondering where to put them up. This will help get me review on my code. We might need to change/optimize the schema and the code accordingly.
[10:38:38] <tanny411>	 Last time, when working with query-parsing, I used `discovery-analytics` repo. But we put the hql command within the airflow job. Is there any place I can save the hql files stand alone? And maybe use them in the airflow jobs later?
[10:43:35] <ejoseph>	 Lunch
[12:01:47] <dcausse>	 tanny411: not sure we have done that before (use a hql file stored somewhere else to create the initial table with airflow), feel free to put it inside the rdf repo for now if it helps (e.g. src/test/resources is it's used in tests) 
[12:02:48] <tanny411>	 @dcausse couldn't we have the hql files stored in the airflow jobs folder and use them?
[12:05:56] <dcausse>	 tanny411: in airflow we can have a standalone file but I'm not sure why this would be helpful?
[12:07:15] <tanny411>	 dcausse: hummm, I was thinking of using that hql file to create the table with a airflow-init job. Previously I just used the hql command as a string withing the job
[12:07:57] <tanny411>	 the file will also serve as a schema for all the tables for now (easier to understand the code if we can see what the end results might look like)
[12:09:01] <tanny411>	 *Previously I just used the hql command as a string within the airflow-job file, and this will also serve as a schema for all the tables for now
[12:09:54] <dcausse>	 so you'd prefer a plain hql file for readability?
[12:20:29] <dcausse>	 tanny411: for now feel free to add a hql file in the airflow/conf folder, we might want to create another folder for hql files but I think we should ask ebernhardson about that 
[12:21:25] <dcausse>	 there might be things like versioning/schema migration that we should care about
[12:45:52] <tanny411>	 dcausse: indeed, wanted a plain hql file. will wait on ebernhardson s reply
[12:59:02] <inflatador>	 Greetings
[13:04:48] <dcausse>	 o/
[13:12:48] <ejoseph>	 o/
[13:16:08] <inflatador>	 <o/
[13:18:27] <inflatador>	 dcausse is this one ready to merge? I see it has a "Work in progress" tag https://gerrit.wikimedia.org/r/c/operations/puppet/+/764830
[13:20:15] <dcausse>	 inflatador: I think we're in state that we can remove the WIP flag and process this patch (it probably has some conflicts to resolve manually tho)
[13:29:55] <inflatador>	 sounds good. I think we can probably merge onto the tip of production. Will give it a try shortly
[13:30:37] <inflatador>	 errr, except I have a security update to install. Guessing I will be offline for 20 mins or so
[13:31:32] <inflatador>	 ...or not, weird. It's now saying I'm up to date?
[13:52:54] <inflatador>	 aand back
[14:18:33] <inflatador>	 OK , the above is merged
[14:22:39] <dcausse>	 thanks!
[14:54:08] <inflatador>	 may be ~5m late to sprint planning
[15:01:11] <gehel>	 ebernhardson, inflatador, ryankemper: triage: https://meet.google.com/eki-rafx-cxi
[15:49:17] <ryankemper>	 oof, phone died
[15:49:19] <ryankemper>	 up now
[15:55:18] <dcausse>	 going offline early, see you tomorrow
[16:35:18] <volans>	 inflatador, ryankemper: do you wanna maybe start the meeting earlier?
[16:35:39] <inflatador>	 volans I'm fine w/it if ryankemper is
[16:36:00] <inflatador>	 should be quick
[16:36:06] <ryankemper>	 volans: inflatador: yeah, i'm good to go in a couple mins
[16:36:22] <volans>	 sgtm, ping when ready and I'll be there
[17:39:24] <inflatador>	 lunch/errands, back in ~1h
[18:38:38] <inflatador>	 and back
[19:51:42] <mpham>	 feeling a bit under the weather today and am going to call it a day early and try to get some rest
[20:04:39] <inflatador>	 <o/
[20:04:43] <inflatador>	 feel better soon!