Skip to content

Conversation

@oceanusxiv
Copy link

Related

What

This is a first stab at enabling more sophisticated ingestion of MCAP files by rerun. It provides the following features

  1. Allowing mcap file paths to be from AWS and GCP as well as local ones.
  2. Allowing special MCAP URL syntax to specify start and end timestamps for loading partial mcap files.

In many ways this is kind of a hack, considering it hijacks the file loading pathway for remote loading. However, I considered this to be less intrusive compared to writing a bespoke cloud mcap data source pathway.

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi! Thanks for opening this pull request.

Because this is your first time contributing to this repository, make sure you've read our Contributor Guide and Code of Conduct.

@oceanusxiv oceanusxiv force-pushed the oceanusxiv/remote_mcap branch from 60dfab9 to e90201e Compare December 7, 2025 19:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant