I'd like to use the Atlas Data Lake with data I've stored in Google Cloud Storage.

I'd like to use the Atlas Data Lake with data I've stored in Microsoft Azure Blob Storage.

I'd like to create visualizations by connecting Power BI to Atlas Data Lake.

Many users of MongoDB store metadata in MDB and PDFs and other files in object storage. With GridFS already built into drivers, it seems like a nice change would allow ADL to federate GridFS functionality across Atlas and the file in object storage

I've started using Online Archive for my data and would not like to add this as a source to my Atlas Data Lake so I can query my cluster + archive + s3 data all together.

I'd like to run an instance of MongoDB's Data Lake product on my own infrastructure.

A lot of providers support the same API of AWS. I think it will be simple to integrate them !

Consider an archive scenario when a user of a given app has not logged into the app in [x] number of weeks/months, so all their data is moved to Online Archive. Once they log back into the app again, their "cold" data should now be considered "hot" and be moved back into Atlas. While we can use $out to copy data back to Atlas, there is no current way to remove the "rehydrated" data from S3 once it's been copied back to Atlas

Add the ability to create a view where the result is pre-computed and is updated incrementally as more data becomes available.

Allow atlas to control on prem instance

Hi Team - With regards to Atlas Data lake and using Online Archive customer request to be able to have (Time + Query) i.e. anything that is older than 60 days that match X query.

You can use the Atlas Data Explorer and Aggregation Builder in the MongoDB Atlas web dashboard on regular collections and views. Unfortunately there appears to be no way to use them against a Data Lake within the web dashboard, either directly or while constructing new Data Sources for Charts. Attempting to use Aggregation Builder on a Data Lake while defining a Data Source forwards to a URL that returns 404.

It would be great if the same functionality was available for Data Lake as well.

Sweden is a very innovative country with many startups and scaleups and AWS is used very often for hosting of services and data. Sweden is also very strict on rules where and how to store data and that is why AWS has eu-north-1 as a location to choose for storing data (which is in Sweden). Currently Data Lake doesn't support that option, the closest one is Germany. It would be great to support eu-north-1 as well, so that we don't have to live with the unnecessary latency.

เห็นพื้นฐานที่สำคัญในการเริ่มต้นใช้พลังงานธรรมชาติสำหรับเทคโนโลยี Bitcoin Cash เป็นบิดาในสกุลเหรียญดิจิตอล Bitcoin ส่วนสำคัญที่ไม่ได้มีคำอธิบายไว้ เนื่องจากรูปแบบความถูกต้องและส่วนต่างในการขโมยเหรียญเป็นส่วนที่จำเป็นต้องดำเนินการกระทำมาจนถึงทุกวันนี้ในการผนึกใช้งาน ถึงแม้จะใช้ไม่ได้ในการซื้อขายเหรียญ Bitcoin Cash แต่มันสามารถปรับให้เหรียญ Bitcoin มีความมันคงและทำลายได้อยากในจำนวนของเหรียญ Bitcoin 21 ล้านเหรียญ และยังแยกเหรียญทองแดง เหรียญเงิน เหรียญทอง เหรียญพิเศษ ไว้เพื่อปรับใช้ในโครงการ แต่การทำงานยังคงยากลำบากเพราะผลบังคับใช้จึ้นอยู่กับความสมัครใจของทุกฝ่าย และในสถานะ CEO เหรียญ Bitcoin พร้อมแหล่งเหมืองเก่่าและที่มายินดีรวมปรับใช้เพื่อความถูกต้อง โปร่งใส เพื่อเป็นทรัพยากรในประเภททรัพย์สินต่อไป

I understand that even with a geo-replicated cluster if that cluster is configured with an online archive and there's a region outage, access to the online archive data is lost. It is still unclear to me if queries against collections configured with online would fail in this scenario. In any case, it would make sense to me to enable the S3 bucket backing the on-line archive to itself be replicated using "Amazon S3 Cross-Region Replication (CRR)"

Ability to import and export archiving rules to be able to restore them if/when we need to restore the cluster. Also useful when replicating prod clusters to our stage environment

Hi,

Today there is no way to partition the archive data based on a field that is of type GUID (legacy GUID). For example, I tried selecting a field which had Binary('0TfYLb3Qg0WT2mZu0wbq8Q==', 3) as the value but I got an error saying that the field is not supported to be a partition field. It makes sense to do this because archived data is usually old and at that time most people were using legacy guids as opposed to object ids.

I'd like the ability to specify when a migration from my Atlas cluster to my Online Archive to take place.

We use Atlas Charts and would like to keep the data moved to Online Archive accessible for reporting/visualizations purposes.