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

Unix Server ( Edge Node ) hangs when there are many jobs running on hadoop cluster started from Unix Edge Node.

  When a unix server or an edge node is running lots of jobs (like Spark, Hadoop, or custom batch processes), crashes happen. For example. For example a process might hit a segementation fault, memory issue or ay other runtime issue. By default, if ulimit -c is not 0, the OS will create core dump. Core dump are written to disk and can be very large, sometimes hundreds of MBs or even GBs per process. What we realized was that when multiple processes crash at the same time, the system suddenly tries to write core files to disk. This was leading to DisK I/O spikes. Thus, node was becoming unresponsive. This was also leading CPU spike because OS was handling crash logging. Setting "ulimit -c 0" disables core dumps. This way we lose ability to debug crashes via core dump But, kept production edge nodes stable. On most Linux systems, by default, "core dumps" are written in current working directory of the process that crashes. Linux allows you to change core dump file nam...




Spring MongoDB Rest API not returning response in 90 seconds which is leading to client timeout

  We have Spring Boot  Rest API deployed in Kubernetes cluster which integrates with MongoDB to fetch the data.  MongoDB is fed with data by a real time Spark & NiFi job.  Our clients complained that for a request what they send they don't have response within 90 seconds. Consider it like an OMS ( Order ManagEment System).  On further analysis, we found that Spark & NiFi processing is happenning within 10 seconds after consuming response data from Kafka. Thus, initally out thought was that it due to delay from upstream to produce data in to Kafka.  Thankfully, our data had create / request  timestamp, and when response was received, and when response was inserted into MongoDB. Subtracting response insert time from request time seemed to be well within 90 seconds. But, still client did timeout on not seeing a response within 90 seconds. This led to confusion on our side.  But, then we realized it was due to Read Preference . We updated this...




MongoDB Regex Query taking more time in Production but same query perform well in UAT

   We came across a situation where-in, MongoDB Query was taking more time in Production like 10 seconds and 4.2 seconds but same query performed well in UAT taking under 400 ms. The very first thought that was evident to us that it is because of amount of data which differed in UAT and Production. Then we ran following to see the execution plan -   db.collection.aggregate(<queries>).explain() This gave us Winning and Rejected Plans. Under which, we analyzed that although it was using 'IXSCAN.' But, it was incorrect index- as we had one compound index built on time field and other fields, and there was other index just on time field for TTL purposes. Winning plan picked TTL index rather than compound index. Thus, we dropped TTL index and built TTL index on a different time field.  That got our query performance time from 10 seconds to 726 ms. Also, for other query the performance came down from 8 seconds to 4.3 seconds. Then, we ran following -  ...




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...




Clone multiple projects or repositories from GitLab under a folder or subfolder.

  Suppose we have a group named as groupA in gitlab, under which we have sub folder structure, and there are multiple projects under a folder.  We wish to clone all the projects under folder. This can be done using gitlab api. Like below -  1) You should have Token for authentication. TOKEN="J612a-xUoMxxcerssRe31_" 2) API URL to subfolder that should give you group id.  API_URL1="https://<gitlab.server.com>/api/v4/groups?search=groupA /dir1/dir2/dir3/dir4" 3) Use below to get group id - GROUP_ID=$(curl --silent --header "Private-Token: $TOKEN" "$API_URL1" | jq -r '.[].id') 4) Now you can fetch and clone all projects by using below - API_URL2="https://<gitlab.server.com>/api/v4/groups/$GROUP_ID/projects" # Fetch repositories list REPOS=$(curl --silent --header "Private-Token: $TOKEN" "$API_URL2" | jq -r '.[].http_url_to_repo') # Clone each repository for REPO in $REPOS; do     git clone $RE...