SeanPT Contributor

We finally cracked this nut this month. Here is a big thing I was missing - the datasets created by the CLI tool or Workbench can have many, many partitions. The limit is MUCH higher than 1500. You still don't want to get stupid with them, but there is more room. Magic can only process 1500 partitions. So when you bring in…

It looks like there is a parquet reader built into the Domo CLI tool.

Yep - I found that and upvoted it.

@AlexF - We have gotten in the habit with a lot of datasets of just expecting that at some point something can go wacky and we can get duplicate data. So we think about data coming in and wonder if there is a way for duplicate data to come in (a script runs twice ... whatever) and build that into our dataflows. Maybe we…

@jaeW_at_Onyx 's video saved my butt because I've gone DEEP down the rabbit hole with Magic v2 and ran face first into needing a BETWEEN JOIN. That trick will absolutely work for me .... for now. I add 48 rows every day. So, a year from now ... sum=[n*(n+1)]/2 153,483,960 rows :/

You're in a good spot, actually. I get very frustrated with how Domo handles datetime data because it makes the assumption that the data coming in is UTC. Assuming your instance has the global setting of a timezone defined, when you bring in the data in Workbench you don't have to do an offset - it will treat it like it is…

Atanas got me going right with that KB article and those URLs. The other URL worked for me.

That link is just dropping me off to a blank page.

Support helped me work through this! 1) The error message is just not a good error message. What it is really saying is "We can't get your file". 2) As of right now the Connector inline help says you can use an HTTP connection. This is not the case. HTTPS is supported. That's why it couldn't get my file. 3) It turns out I…

Oof. I think I'd rather just use python to parse the data and spit out a CSV. I already used Python to remove the brackets that the connector doesn't like but now it puked on the next bit.

Unfortunately that wasn't the case. I ended up backing up the registry and then deleting the WindowLayout and JobGridLayout keys. Once I restarted workbench, my GUI was reset and I was good to go. Once it was reset I could see what you and support were talking about but that wasn't my issue.