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.

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.

I would like by Data Lake in Project A to be able to query data in a Cluster in Project B.

The "Date field to archive on" option under Archiving Rule tab in Online Archive should also accept date field having timestamp format instead of only having date format.

I have a custom log format that I'd like to be able query. I imagine I would describe the format of the text files to Atlas Data Lake and then be able to query them.

User friendly data filtering, queries for updating or deleting data from collections.

I need to specify the delimiter for my CSV files.