Skip to content

utilization of parquet for intermediate storageย #26

@jr3cermak

Description

@jr3cermak

There are several steps involved in migration to parquet for intermediate processing of slocum glider data.

Is there a particular storage pattern or design desired for the parquet data structures?
REF: https://arrow.apache.org/docs/python/parquet.html#parquet-file-writing-options

  • Enforce version 2.4? 2.6?
  • Ensure the structure is queryable by time for speedy subsetting?
  • If enforcing 2.6, timestamp units become less an issue
  • Partitioning? Glider ID, Deployment ID, Process method (rt vs. delayed), QC'd (Level 0, 1, ...)

Have to nail down a potential dbdreader issue first.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions