Make `DataTypeSizes` easy to read from the application conifguration

Open
  • Is something wrong?
#12 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
scala, spark
Domain
data-engineering

Research direction

Start by locating DataTypeSizes and the application's existing configuration entry points; the issue does not name files or tests. Determine how configured values should override the current sizes, and consider the work done when an application can read DataTypeSizes values from configuration.

Written by the indexing model from the issue text.

Description

enhancement

Background

DataTypeSizes can vastly wary between application even datasets.

Feature

Make it easy to read the values from configuration.

Dominant language
Scala
Stars
9
Forks
2
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AbsaOSS/spark-partition-sizing

All issues in AbsaOSS/spark-partition-sizing

Similar issues

More Scala issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.