Hello, we’re just getting started with GoodData an...
# gooddata-cloud
o
Hello, we’re just getting started with GoodData and are currently setting up our data pipeline. Our goal is to flow data from MongoDB into AWS Redshift, which will serve as the source for GoodData. However, our MongoDB documents are quite complex, including a lot of embedded object arrays. We’re looking for best practices or a cheatsheet to help streamline this process and make it more efficient. Any guidance or resources would be greatly appreciated!
m
Hi Oscar, sorry for the delay in getting back to you here - But as you’re aware both MongoDB and AWS Redshift are not our technologies so there is not much guidance we can provide in this case - But I found some articles online which you might find useful: https://medium.com/@subhampradhan966/efficiently-migrating-data-from-mongodb-to-aws-redshift-with-s3-and-glue-jobs-a-comprehensive-cff2c4b1ef87 https://github.com/mongodb-partners/Atlas_to_Redshift https://aws.amazon.com/documentdb/migrating-self-managed-mongodb-databases/ You can also find many more articles online which might help you Other than this, the other option would be to loop in your Account Owner to discuss with you the possibility of opting for GoodData’s Professional Services and our engineers can help you with this setup.
o
thanks
After reviewing the links, we’ve already implemented most of the recommended steps. However, our primary challenge remains the labor-intensive process of mapping the embedded document arrays. We’re seeking insights or tips from anyone who has experience handling this specific task.
i
Hey Oscar, as mentioned by my colleague Michael above, this is bit out of our scope. I'd suggest to check also some MongoDB and AWS Redshift forums as you might get more valuable tips there. Fingers crossed for you!
o
Thanks @Ivana Gasparekova