-
Notifications
You must be signed in to change notification settings - Fork 393
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stable key order for map vectorizers #88
Conversation
…ys being naturally sorted now
Codecov Report
@@ Coverage Diff @@
## master #88 +/- ##
==========================================
+ Coverage 85.97% 85.98% +0.01%
==========================================
Files 294 294
Lines 9547 9548 +1
Branches 352 336 -16
==========================================
+ Hits 8208 8210 +2
+ Misses 1339 1338 -1
Continue to review full report at Codecov.
|
@@ -124,14 +123,14 @@ class IntegralMapVectorizer[T <: OPMap[Long]](uid: String = UID[IntegralMapVecto | |||
def setFillWithMode(shouldFill: Boolean): this.type = set(withConstant, !shouldFill) | |||
|
|||
override def fillByKey(dataset: Dataset[Seq[T#Value]]): Seq[Map[String, Double]] = { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: it looks like fillByKey in RealMapVectorizer
and IntegralMapVectorizer
have a very small diff. Maybe refactor.
Related issues
Map vectorizers do not order the keys properly.
Describe the proposed solution
MapVectorizerFuns.getKeyValues
function.Describe alternatives you've considered
N/A