Skip to content

Introduce PartitionEntry class to represent stats per partition #8455

Closed as not planned

Description

@ajantha-bhat

Feature Request / Improvement

In the design, The schema of partitions metadata table and partition stats file is kept to be same

Hence, move PartitionsTable.Partition to a separate class and re-use them for partition stats.
We also need to extend PartitionsTable.Partition this class to org.apache.avro.generic.IndexedRecord to make this class compatible to directly write and read from ParquetAvroWriter and ParquetValueReaders

Introduce PartitionEntry class to represent stats per partition. This should be independent of PartitionsTable

Query engine

None

Activity

  1. changed the title [-]Move PartitionsTable.Partition to a separate class and re-use them for partition stats.[/-] [+]Introduce PartitionEntry class to represent stats per partition[/+] on Jan 4, 2024
  2. github-actions commented on Sep 15, 2024

    @github-actions

    This issue has been automatically marked as stale because it has been open for 180 days with no activity. It will be closed in next 14 days if no further activity occurs. To permanently prevent this issue from being considered stale, add the label 'not-stale', but commenting on the issue is preferred when possible.

  3. github-actions commented on Oct 5, 2024

    @github-actions

    This issue has been closed because it has not received any activity in the last 14 days since being marked as 'stale'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions