Tableau Prep Flows Should Stop Failing #Tableau #TableauPrep #TableauCloud

0:00Tableau Prep Hyper as a Service.

0:02Now this is interesting.

0:02The process larger Prep flows more efficiently with Hyper as a Service.

0:06Tableau Prep will now separate the flow processor, Minerva, and Hyper into different pods, allowing services to be scaled and deployed independently.

0:14This will make it easier to isolate faults and allocate resources effectively, resulting in far fewer flow failures due to memory constraints.

0:24Hypers as a service is generally available in tabay prep and cloud.

0:29So this is interesting.

0:31I don't know what this actually means, but what I think is happening is that they're just making the architecture of Tableau Prep on Tableau Cloud, specifically Tableau Prep Conductor.

0:41run a little bit better which means that when you run out of memory or there are memory challenges it's going to fail more gracefully and still complete the jobs.

0:49And by separating out the services, so flow presses of Minerva and Hyper into different pods, essentially putting them on different compute clusters.

0:58That means there's less chance of one cluster running out of memory more easily.

1:02Which these are these two are probably going to be the biggest ones.

1:04Hyper is obviously your data

1:05And the flow processor is actually think of it as like the backgrounder for Tableau Prep.

1:09So this is kind of nice.

1:10It's also good to have the actual code name for it.

1:13That's kind of nice.

1:13I never knew that was the name, so that's kind of kind of cool.

1:16Okay