[
https://issues.apache.org/jira/browse/SPARK-2354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14060521#comment-14060521
]
Sean Owen commented on SPARK-2354:
----------------------------------
Yes, you could not just naively flip all the bits to make a new complement
BitSet. These methods don't exist, right? And the resulting size of the new
BitSet would still be the same. If you're just saying these methods in the
future would need to be implemented correctly, that's true. Is there an issue
to report on current code?
> BitSet Range Expanded when creating new one
> -------------------------------------------
>
> Key: SPARK-2354
> URL: https://issues.apache.org/jira/browse/SPARK-2354
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Affects Versions: 1.0.0, 1.1.0
> Reporter: Yijie Shen
> Priority: Minor
>
> BitSet has a constructor parameter named "numBits: Int" and indicate the bit
> num inside.
> And also, there is a function called "capacity" which represents the long
> words number to hold the bits.
> When creating new BitSet,for example in '|', I thought the new created one
> shouldn't be the size of longer words' length, instead, it should be the
> longer set's num of bit
> {code}def |(other: BitSet): BitSet = {
> val newBS = new BitSet(math.max(numBits, other.numBits))
> // I know by now the numBits isn't a field
> {code}
> Does it have any other reason to expand the BitSet range I don't know?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
