[jira] [Assigned] (SPARK-46173) Skipping trimAll call in stringToDate functions to avoid needless string copy
[ https://issues.apache.org/jira/browse/SPARK-46173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wenchen Fan reassigned SPARK-46173: --- Assignee: Aleksandar Tomic > Skipping trimAll call in stringToDate functions to avoid needless string copy > - > > Key: SPARK-46173 > URL: https://issues.apache.org/jira/browse/SPARK-46173 > Project: Spark > Issue Type: Improvement > Components: SQL >Affects Versions: 3.0.0 >Reporter: Aleksandar Tomic >Assignee: Aleksandar Tomic >Priority: Major > Labels: pull-request-available > > In StringToDate function call we currently first call trimAll to remove any > whitespace and isocontrol characters. Trimming results in copying the input > string which is not really needed given that we can do all the parsing in > place by just skipping the whitespace/isocontrol chars. > Given that we have customers complaining about speed of stringtodate > function, especially when input string is long/potentially malformed proposal > is to skip trimAll call and do parsing in place. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Assigned] (SPARK-46173) Skipping trimAll call in stringToDate functions to avoid needless string copy
[ https://issues.apache.org/jira/browse/SPARK-46173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot reassigned SPARK-46173: -- Assignee: (was: Apache Spark) > Skipping trimAll call in stringToDate functions to avoid needless string copy > - > > Key: SPARK-46173 > URL: https://issues.apache.org/jira/browse/SPARK-46173 > Project: Spark > Issue Type: Improvement > Components: SQL >Affects Versions: 3.0.0 >Reporter: Aleksandar Tomic >Priority: Major > Labels: pull-request-available > > In StringToDate function call we currently first call trimAll to remove any > whitespace and isocontrol characters. Trimming results in copying the input > string which is not really needed given that we can do all the parsing in > place by just skipping the whitespace/isocontrol chars. > Given that we have customers complaining about speed of stringtodate > function, especially when input string is long/potentially malformed proposal > is to skip trimAll call and do parsing in place. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Assigned] (SPARK-46173) Skipping trimAll call in stringToDate functions to avoid needless string copy
[ https://issues.apache.org/jira/browse/SPARK-46173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot reassigned SPARK-46173: -- Assignee: Apache Spark > Skipping trimAll call in stringToDate functions to avoid needless string copy > - > > Key: SPARK-46173 > URL: https://issues.apache.org/jira/browse/SPARK-46173 > Project: Spark > Issue Type: Improvement > Components: SQL >Affects Versions: 3.0.0 >Reporter: Aleksandar Tomic >Assignee: Apache Spark >Priority: Major > Labels: pull-request-available > > In StringToDate function call we currently first call trimAll to remove any > whitespace and isocontrol characters. Trimming results in copying the input > string which is not really needed given that we can do all the parsing in > place by just skipping the whitespace/isocontrol chars. > Given that we have customers complaining about speed of stringtodate > function, especially when input string is long/potentially malformed proposal > is to skip trimAll call and do parsing in place. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Assigned] (SPARK-46173) Skipping trimAll call in stringToDate functions to avoid needless string copy
[ https://issues.apache.org/jira/browse/SPARK-46173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot reassigned SPARK-46173: -- Assignee: Apache Spark > Skipping trimAll call in stringToDate functions to avoid needless string copy > - > > Key: SPARK-46173 > URL: https://issues.apache.org/jira/browse/SPARK-46173 > Project: Spark > Issue Type: Improvement > Components: SQL >Affects Versions: 3.0.0 >Reporter: Aleksandar Tomic >Assignee: Apache Spark >Priority: Major > Labels: pull-request-available > > In StringToDate function call we currently first call trimAll to remove any > whitespace and isocontrol characters. Trimming results in copying the input > string which is not really needed given that we can do all the parsing in > place by just skipping the whitespace/isocontrol chars. > Given that we have customers complaining about speed of stringtodate > function, especially when input string is long/potentially malformed proposal > is to skip trimAll call and do parsing in place. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Assigned] (SPARK-46173) Skipping trimAll call in stringToDate functions to avoid needless string copy
[ https://issues.apache.org/jira/browse/SPARK-46173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot reassigned SPARK-46173: -- Assignee: (was: Apache Spark) > Skipping trimAll call in stringToDate functions to avoid needless string copy > - > > Key: SPARK-46173 > URL: https://issues.apache.org/jira/browse/SPARK-46173 > Project: Spark > Issue Type: Improvement > Components: SQL >Affects Versions: 3.0.0 >Reporter: Aleksandar Tomic >Priority: Major > Labels: pull-request-available > > In StringToDate function call we currently first call trimAll to remove any > whitespace and isocontrol characters. Trimming results in copying the input > string which is not really needed given that we can do all the parsing in > place by just skipping the whitespace/isocontrol chars. > Given that we have customers complaining about speed of stringtodate > function, especially when input string is long/potentially malformed proposal > is to skip trimAll call and do parsing in place. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Assigned] (SPARK-46173) Skipping trimAll call in stringToDate functions to avoid needless string copy
[ https://issues.apache.org/jira/browse/SPARK-46173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot reassigned SPARK-46173: -- Assignee: Apache Spark > Skipping trimAll call in stringToDate functions to avoid needless string copy > - > > Key: SPARK-46173 > URL: https://issues.apache.org/jira/browse/SPARK-46173 > Project: Spark > Issue Type: Improvement > Components: SQL >Affects Versions: 3.0.0 >Reporter: Aleksandar Tomic >Assignee: Apache Spark >Priority: Major > Labels: pull-request-available > > In StringToDate function call we currently first call trimAll to remove any > whitespace and isocontrol characters. Trimming results in copying the input > string which is not really needed given that we can do all the parsing in > place by just skipping the whitespace/isocontrol chars. > Given that we have customers complaining about speed of stringtodate > function, especially when input string is long/potentially malformed proposal > is to skip trimAll call and do parsing in place. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Assigned] (SPARK-46173) Skipping trimAll call in stringToDate functions to avoid needless string copy
[ https://issues.apache.org/jira/browse/SPARK-46173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot reassigned SPARK-46173: -- Assignee: (was: Apache Spark) > Skipping trimAll call in stringToDate functions to avoid needless string copy > - > > Key: SPARK-46173 > URL: https://issues.apache.org/jira/browse/SPARK-46173 > Project: Spark > Issue Type: Improvement > Components: SQL >Affects Versions: 3.0.0 >Reporter: Aleksandar Tomic >Priority: Major > Labels: pull-request-available > > In StringToDate function call we currently first call trimAll to remove any > whitespace and isocontrol characters. Trimming results in copying the input > string which is not really needed given that we can do all the parsing in > place by just skipping the whitespace/isocontrol chars. > Given that we have customers complaining about speed of stringtodate > function, especially when input string is long/potentially malformed proposal > is to skip trimAll call and do parsing in place. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Assigned] (SPARK-46173) Skipping trimAll call in stringToDate functions to avoid needless string copy
[ https://issues.apache.org/jira/browse/SPARK-46173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot reassigned SPARK-46173: -- Assignee: (was: Apache Spark) > Skipping trimAll call in stringToDate functions to avoid needless string copy > - > > Key: SPARK-46173 > URL: https://issues.apache.org/jira/browse/SPARK-46173 > Project: Spark > Issue Type: Improvement > Components: SQL >Affects Versions: 3.0.0 >Reporter: Aleksandar Tomic >Priority: Major > Labels: pull-request-available > > In StringToDate function call we currently first call trimAll to remove any > whitespace and isocontrol characters. Trimming results in copying the input > string which is not really needed given that we can do all the parsing in > place by just skipping the whitespace/isocontrol chars. > Given that we have customers complaining about speed of stringtodate > function, especially when input string is long/potentially malformed proposal > is to skip trimAll call and do parsing in place. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Assigned] (SPARK-46173) Skipping trimAll call in stringToDate functions to avoid needless string copy
[ https://issues.apache.org/jira/browse/SPARK-46173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot reassigned SPARK-46173: -- Assignee: Apache Spark > Skipping trimAll call in stringToDate functions to avoid needless string copy > - > > Key: SPARK-46173 > URL: https://issues.apache.org/jira/browse/SPARK-46173 > Project: Spark > Issue Type: Improvement > Components: SQL >Affects Versions: 3.0.0 >Reporter: Aleksandar Tomic >Assignee: Apache Spark >Priority: Major > Labels: pull-request-available > > In StringToDate function call we currently first call trimAll to remove any > whitespace and isocontrol characters. Trimming results in copying the input > string which is not really needed given that we can do all the parsing in > place by just skipping the whitespace/isocontrol chars. > Given that we have customers complaining about speed of stringtodate > function, especially when input string is long/potentially malformed proposal > is to skip trimAll call and do parsing in place. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org