跳至主要内容

Functional scala Try Success Failure and for composition

 Lesson learn Scala programming

I got some Scala to write in a recent spark related project. Specially, the Scala UDF (aka. user defined function) to be used in spark application.

I got a feel that Try, Success, Failure is not very useful until being applied to the For Comprehensions for automatically unpacking. Refer to the following code example (inspired by StackOverFlow Post)

import java.sql.Timestamp
import org.apache.spark.sql.functions.udf
import scala.util.{Try, Success, Failure}

// combine time_date and time_time for a timestamp in UTC.
val time_to_ts: ((String, String) => Option[Timestamp]) = (time_date, time_time) => {

  val time_time_a = time_time.split(':')
  val ts = for (
    y <- Try(time_date.take(4).toInt);              // toInt exception
    m <- Try(time_date.take(6).takeRight(2).toInt); // toInt exception
    d <- Try(time_date.take(8).takeRight(2).toInt); // toInt exception
    tsymd <- Try(Timestamp.valueOf(s"$y-$m-$d 0:0:0.0").getTime()); // parsing
                                    // exception

    h <- Try(time_time_a(0));  // index exception
    M <- Try(time_time_a(1));  // ditto
    s <- Try(time_time_a(2));  // ditto
    ms <- Try(time_time_a(3)); // ditto
    tshmsms <- Try(Timestamp.valueOf(s"1970-1-1 $h:$M:$s.$ms").getTime()); // parsing
                                       // exception

    ts <- Try(new Timestamp(tsymd - 3600 * 1000 * 8 + tshmsms)) // construct
                                // exception
  ) yield ts

  ts match {
    case Success(timestamp) => Some(timestamp)
    case Failure(_) => None
  }
}

val getTs = udf(time_to_ts)

Why not use built-in functions?

Since the spark built-in datatime, timestamp family of functions when used to convert string to internal timestamp. Will lose the ****miliseconds**** field, which is critical to our use case.

 

评论

此博客中的热门博文

Eglot and before/after-save-hook and use-package

In Emacs, when you try to automate some actions during every save action, you will surely get to the before-save-hook and the after-save-hook. Simply adding something like gofmt-before-save to before-save-hook will save you tons of time to do the go-fmt. And then, I meet eglot, and gopls will also save me tons of time doing googling and api documentation navigation. But eglot-ensure is not very friendly to the good old ways of how after-save-hooks were designed to work. It makes the before/after-save-hook a buffer local variable and it does not inherit the variable's global value. So, to make before/after-save-hook work again, experts start to adding hooks to major mode specific hooks like this: emacs.md - Go (opensource.google) """ ;; Optional: install eglot-format-buffer as a save hook. ;; The depth of -10 places this before eglot's willSave notification, ;; so that that notification reports the actual contents that will be saved. (defu...

Use MobaDiff with git difftool

Recently there's an activity in IT that forces the deletion of all unauthorized softwares from all work machines. Unfortunately, kdiff3 is one in the list. As it is generally okay to use vimdiff as an alternative for kdiff3, A gui tool is better suited for desktop workflows. Known that MobaXterm is shipping a gui diff tool named MobaDiff. But it only appears in the windows right click context menu. Find the real application name takes me some time to search in the windows registry. "MobaRTE.exe", which is the one invoked by HKCR\*\shell\MobaDiff. And it was invoked with "-contextdiff" switch to show MobaDiff UI, while when the switch is "-contextedit" it shows MobaTextEditor. Too bad that the "-contextdiff" switch do not support pre-image post-image as other diff tool did, which effectively made it unable to be used as a command line diff utility. Also MobaTech did not mention anything in their document of this Mob...