unitycatalog / unitycatalog/unitycatalog

Suggest to make unitycatalog to be a pure Java repository

Open
#1,101 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
3.5k
Forks
672
Avg merge
6d 16h
Merged PRs (30d)
30

Description

Currently, the unitycatalog is mixed by Java and Scala code, while 90% of the code is Java code. I can only see 3 files are Scala code.

find . -type f -name '*.scala' 
./connectors/spark/src/main/scala/io/unitycatalog/spark/UCSingleCatalog.scala
./project/Tarball.scala
./project/PythonClientPostBuild.scala
./project/ReleaseSettings.scala

Personally, I will suggest to turn the unitycatalog to be a pure java repository, which will make us easier to manage the whole dev loop. For example, all of the following dev loop can focus only on Java

  • Codestyle enforcement
  • Github CI testing
  • Test framework and abstraction.

Also if we finally turn to pure java repo, then we also don't need to be distract for different Scala compatible issues.

Contributor guide

Open the contributing guide

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.

Research direction

Start by reviewing the Scala files listed in the issue: connectors/spark/src/main/scala/io/unitycatalog/spark/UCSingleCatalog.scala and the project/*.scala files. Then inspect the repository’s CI, codestyle, test, and build configuration to determine the scope of removing Scala. Done means the repository’s Java-only direction and any required handling of these files are agreed and implemented.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, scala
Domain
build-system, developer-experience
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.