RumbleDB / RumbleDB/rumble

RumbleML: Disable Utility Transformers

Open
#562 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Enhancement RumbleML
Dominant language
Java
Stars
246
Forks
85
Avg merge
6d 1h
Merged PRs (30d)
22

Description

ColumnPruner and VectorAttributeRewriter are utility methods for Vectors and probably don't need to be exposed to the end user of Rumble. If so, disable them.

Note: Vector size hint also appears like a utility method as vectors are merely an underlying detail in Rumble.
What should we do about this?

Also VectorSlicer

Contributor guide

No contributing guide indexed for this repository

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

Review how ColumnPruner, VectorAttributeRewriter, VectorSizeHint, and VectorSlicer are exposed in RumbleML, then compare that surface with the linked Spark ML descriptions. Done means a documented decision for each named transformer and an agreed scope for disabling any utilities.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
machine-learning
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
18/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.