Forum Discussion
winosky
5 years agoNew Contributor III
Hi @Supratim, it’s a copy of json from a execute snap into a aggregate. I believe the aggregate may be the problem, I’ve read it was resource intensive so I need to find an alternate solution.
tlikarish
5 years agoEmployee
If you can post a pipeline and small data set that reproduces the issue, I can take a look at it. Otherwise, you could reach out to support for additional help.
- winosky5 years agoNew Contributor III
Thanks @tlikarish, I’ve already altered the pipeline and things are looking better. I had to avoid using the copy snap and aggregate or at least minimize the data set before it got to the aggregate.