Mailing-List: contact issues-help@spark.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 27 Feb 2017 16:53:45 +0000 (UTC)
From: "Bill Chambers (JIRA)" <jira@apache.org>
To: issues@spark.apache.org
Message-ID: <JIRA.13045704.1487874417000.7778.1488214425430@Atlassian.JIRA>
In-Reply-To: <JIRA.13045704.1487874417000@Atlassian.JIRA>
References: <JIRA.13045704.1487874417000@Atlassian.JIRA> <JIRA.13045704.1487874417693@jira-lw-us.apache.org>
Subject: [jira] [Commented] (SPARK-19714) Bucketizer Bug Regarding Handling
 Unbucketed Inputs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 27 Feb 2017 16:53:50 -0000


    [ https://issues.apache.org/jira/browse/SPARK-19714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15886109#comment-15886109 ] 

Bill Chambers commented on SPARK-19714:
---------------------------------------

Agree with your first and second paragraphs.

Regarding the third, it's worth a discussion certainly, but it's a pretty big departure from the current definition which is worrisome.

> Bucketizer Bug Regarding Handling Unbucketed Inputs
> ---------------------------------------------------
>
>                 Key: SPARK-19714
>                 URL: https://issues.apache.org/jira/browse/SPARK-19714
>             Project: Spark
>          Issue Type: Bug
>          Components: ML, MLlib
>    Affects Versions: 2.1.0
>            Reporter: Bill Chambers
>
> {code}
> contDF = spark.range(500).selectExpr("cast(id as double) as id")
> import org.apache.spark.ml.feature.Bucketizer
> val splits = Array(5.0, 10.0, 250.0, 500.0)
> val bucketer = new Bucketizer()
>   .setSplits(splits)
>   .setInputCol("id")
>   .setHandleInvalid("skip")
> bucketer.transform(contDF).show()
> {code}
> You would expect that this would handle the invalid buckets. However it fails
> {code}
> Caused by: org.apache.spark.SparkException: Feature value 0.0 out of Bucketizer bounds [5.0, 500.0].  Check your features, or loosen the lower/upper bound constraints.
> {code} 
> It seems strange that handleInvalud doesn't actually handleInvalid inputs.
> Thoughts anyone?


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org