Skip to main content

Scala - Scalable Language

Scala, short for Scalable Language-
•             Created by Martin Odersky
•             Is object-oriented & functional Programming language
•             Scala runs on the JVM
Installations
•             Install Java
•             Set Your Java Environment. Ex- JAVA_HOME, PATH, etc
•             Install Scala
•             After installation, verify version by typing on command prompt or shell
>scala –version
>java –version
If you have a good understanding on Java, then it will be very easy for you to learn Scala. But, we would again describe basics as below –
  1. Object - Have states and behaviors. Ex- A dog is black Color (State) and it is honest (behavior) than Humans
  2. Class – Behaviors & states can be defined in a template. This template is your class. For example – Class “Living Being” defines state Legs and various Objects can have different states 0, 1, 2, 3 or 4 Legs.
  3. Methods – It is basically a behavior. It is in methods where the logics are written, data is manipulated and all the actions are executed.
  4. Fields – Object variables are called fields. An object's state is created by the values assigned to these fields.
  5. Closure - A closure is a function, whose return value depends on the value of one or more variables declared outside this function.
  6. Traits - A trait encapsulates method and field definitions. Traits are used to define object types by specifying the signature of the supported methods.
How to run –
  • Either use or external Editor. For example Eclipse, etc.
  • Or, Use Interactive Method-
    1. Open the command prompt
    2. Execute command "scala"
Welcome to Scala version 2.11.7 (Java HotSpot(TM) Client VM, Java 1.7.0_25).
Type in expressions to have them evaluated.
Type :help for more information.

scala> println("Hello, Scala")
Hello, Scala

  • Or Script Mode
  • Open Notepad write below code & save as HelloWorld.scala

object HelloWorld {
   /* This is my first java program. 
   * This will print 'Hello World' as the output
   */
   def main(args: Array[String]) {
      println("Hello, world!") // prints Hello World
   }
}

  • Open the command prompt 
  • Use scalac’ command to compile the Scala program 

> scalac HelloWorld.scala

  • Use ‘scala’ command to run bytecode on JVM

> scala HelloWorld

Hello, World!

Scala has some coding conventions that should be followed while Programming –
  • Case Sensitivity - Identifier Dinesh & dinesh is different.
  • Class Names – First Letter of name in upper Case. And if multiple words then follow camel case.
  • Method Names - Start with a Lower Case letter. And if multiple words then follow camel case.
  • Program File Name – Name of Object class and File should be same with an extension “.scala”
  • Program execution starts from the main() method which is a mandatory part of every Scala Program. 



Comments

Popular posts

Spark MongoDB Connector Not leading to correct count or data while reading

  We are using Scala 2.11 , Spark 2.4 and Spark MongoDB Connector 2.4.4 Use Case 1 - We wanted to read a Shareded Mongo Collection and copy its data to another Mongo Collection. We noticed that after Spark Job successful completion. Output MongoDB did not had many records. Use Case 2 -  We read a MongoDB collection and doing count on dataframe lead to different count on each execution. Analysis,  We realized that MongoDB Spark Connector is missing data on bulk read as a dataframe. We tried various partitioner, listed on page -  https://www.mongodb.com/docs/spark-connector/v2.4/configuration/  But, none of them worked for us. Finally, we tried  MongoShardedPartitioner  this lead to constant count on each execution. But, it was greater than the actual count of records on the collection. This seems to be limitation with MongoDB Spark Connector. But,  MongoShardedPartitioner  seemed closest possible solution to this kind of situation. But, it per...




Scala Spark building Jar leads java.lang.StackOverflowError

  Exception -  [Thread-3] ERROR scala_maven.ScalaCompileMojo - error: java.lang.StackOverflowError [Thread-3] INFO scala_maven.ScalaCompileMojo - at scala.collection.generic.TraversableForwarder$class.isEmpty(TraversableForwarder.scala:36) [Thread-3] INFO scala_maven.ScalaCompileMojo - at scala.collection.mutable.ListBuffer.isEmpty(ListBuffer.scala:45) [Thread-3] INFO scala_maven.ScalaCompileMojo - at scala.collection.mutable.ListBuffer.toList(ListBuffer.scala:306) [Thread-3] INFO scala_maven.ScalaCompileMojo - at scala.collection.mutable.ListBuffer.result(ListBuffer.scala:300) [Thread-3] INFO scala_maven.ScalaCompileMojo - at scala.collection.mutable.Stack$StackBuilder.result(Stack.scala:31) [Thread-3] INFO scala_maven.ScalaCompileMojo - at scala.collection.mutable.Stack$StackBuilder.result(Stack.scala:27) [Thread-3] INFO scala_maven.ScalaCompileMojo - at scala.collection.generic.GenericCompanion.apply(GenericCompanion.scala:50) [Thread-3] INFO scala_maven.ScalaCompile...




MongoDB Chunk size many times bigger than configure chunksize (128 MB)

  Shard Shard_0 at Shard_0/xyz.com:27018 { data: '202.04GiB', docs: 117037098, chunks: 5, 'estimated data per chunk': '40.4GiB', 'estimated docs per chunk': 23407419 } --- Shard Shard_1 at Shard_1/abc.com:27018 { data: '201.86GiB', docs: 116913342, chunks: 4, 'estimated data per chunk': '50.46GiB', 'estimated docs per chunk': 29228335 } Per MongoDB-  Starting in 6.0.3, we balance by data size instead of the number of chunks. So the 128MB is now only the size of data we migrate at-a-time. So large data size per chunk is good now, as long as the data size per shard is even for the collection. refer -  https://www.mongodb.com/community/forums/t/chunk-size-many-times-bigger-than-configure-chunksize-128-mb/212616 https://www.mongodb.com/docs/v6.0/release-notes/6.0/#std-label-release-notes-6.0-balancing-policy-changes




AWS EMR Spark – Much Larger Executors are Created than Requested

  Starting EMR 5.32 and EMR 6.2 you can notice that Spark can launch much larger executors that you request in your job settings. For example - We started a Spark Job with  spark.executor.cores  =   4 But, one can see that the executors with 20 cores (instead of 4 as defined by spark.executor.cores) were launched. The reason for allocating larger executors is that there is a AWS specific Spark option spark.yarn.heterogeneousExecutors.enabled (exists in EMR only, does not exist in Open Source Spark) that is set to true by default that combines multiple executor creation requests on the same node into a larger executor container. So as the result you have fewer executor containers than you expected, each of them has more memory and cores that you specified. If you disable this option (--conf "spark.yarn.heterogeneousExecutors.enabled=false"), EMR will create containers with the specified spark.executor.memory and spark.executor.cores settings and will not co...




Hive Count Query not working

Hive with Tez execution engine -  count(*) not working , returning 0 results.  Solution -  set hive.compute.query.using.stats=false Refer -  https://cwiki.apache.org/confluence/display/Hive/Configuration+Properties hive.compute.query.using.stats Default Value:  false Added In: Hive 0.13.0 with  HIVE-5483 When set to true Hive will answer a few queries like min, max, and count(1) purely using statistics stored in the metastore. For basic statistics collection, set the configuration property  hive.stats.autogather   to true. For more advanced statistics collection, run ANALYZE TABLE queries.