Skip to main content



Design Patterns (aka DP), Creational - Factory Pattern

DP is a well-described solution to a common software problem. Its benefits:

  • Already defined to solve a problem.
  • Increase code reusability and robustness.
  • Faster devlopment and new developers in team can understand it easily
DP defined in to 3 categories:
  • Creational - Used to construct objects such that they can be decoupled from their implementing system.
  • Structural - Used to form large object structures between many disparate objects
  • Behavioral - Used to manage algorithms, relationships, and responsibilities between objects.
  • Factory - Exposes a method for creating objects, allowing sub-classes to control the actual creation process.
Consider a scenario as below:-
  • You have an interface or abstract class or a normal class. Computer class
  • There are 2 sub-classes of of Computer. PC class and Server class
  • Now you have a factory which provides you Computers. And you can give specification to factory whether you want a PC or Server.
Below code implements above scenario:

package com.test.command.dp.creational.factory;

/**Abstract class**/ 
public abstract class Computer {

       public abstract String getRAM();

       public abstract String getHDD();

       public abstract String getCPU();

       @Override
       public String toString() {

              return "RAM= " + this.getRAM() + ", HDD=" + this.getHDD() + ", CPU="
                           + this.getCPU();
       }

}

package com.test.command.dp.creational.factory;

public class PC extends Computer {

       private String ram;
       private String hdd;
       private String cpu;

       public PC(String ram, String hdd, String cpu) {
              this.ram = ram;
              this.hdd = hdd;
              this.cpu = cpu;
       }

       @Override
       public String getRAM() {
              // TODO Auto-generated method stub
              return this.ram;
       }

       @Override
       public String getHDD() {
              // TODO Auto-generated method stub
              return this.hdd;
       }

       @Override
       public String getCPU() {
              // TODO Auto-generated method stub
              return this.cpu;
       }

}

package com.test.command.dp.creational.factory;

public class Server extends Computer {

       private String ram;
       private String hdd;
       private String cpu;
      
      

       public Server(String ram, String hdd, String cpu) {
             
              this.ram = ram;
              this.hdd = hdd;
              this.cpu = cpu;
       }

       @Override
       public String getRAM() {
              // TODO Auto-generated method stub
              return this.ram;
       }

       @Override
       public String getHDD() {
              // TODO Auto-generated method stub
              return this.hdd;
       }

       @Override
       public String getCPU() {
              // TODO Auto-generated method stub
              return this.cpu;
       }

}

package com.test.command.dp.creational.factory;

/**Factory**/
public class ComputerFactory {

       public static Computer getComputer(String type, String ram, String hdd, String cpu){
              if("PC".equalsIgnoreCase(type)){
                     return new PC(ram, hdd, cpu);
              }
              else if("Server".equalsIgnoreCase(type)){
                     return new Server(ram, hdd, cpu);
              }
              return null;
       }
      
       public static void main(String[] args) {
              Computer pc = ComputerFactory.getComputer("PC", null, null, null);
              Computer server = ComputerFactory.getComputer("SERVER", "12", null, null);
             
              System.out.println("Your PC Dinesh Sachdev. Delivered to Indore:"+pc);
              System.out.println("Your Server Dinesh Sachdev. Delivered to Indore:"+server);
       }
}

Comments

Post a Comment

Popular posts

Spring MongoDB Rename field with derived Value of another field

Input Collection -  [ { 'k' : 'Troubleshooting' , 'hour' : '2024-10-10T16' , 'v' : [ 'WebPage, Login' ] }, { 'k' : 'TroubleshootingMe' , 'hour' : '2024-10-07T01' , 'v' : [ 'Accounts, etc' ] }  ] Expected Output -  [ { 'hour' : '2024-10-10T16' , 'Troubleshooting' : [ 'WebPage, Login' ] }, { 'hour' : '2024-10-07T01' , 'TroubleshootingMe' : [ 'Accounts, etc' ] }  ]   Above Can be achieved by  $replaceRoot / $replaceWith as follows - { $replaceWith : { $mergeObjects : [ { hour : "$hour" }, { "$arrayToObject" : [ [ { k : "$k" , v : "$v" } ] ] } ] } } or { $replaceRoo...
Post a Comment
Read more




What is Leadership

 
Post a Comment
Read more




Spark Error - missing part 0 of the schema, 2 parts are expected

 Exception -  Caused by: org.apache.spark.sql.AnalysisException : Could not read schema from the hive metastore because it is corrupted. (missing part 0 of the schema, 2 parts are expected).; Analysis -  ·          Check for table definition. In TBLProperties, you might find something like this – > spark.sql.sources.schema.numPartCols > 'spark.sql.sources.schema.numParts' 'spark.sql.sources.schema.part.0' > 'spark.sql.sources.schema.part.1' 'spark.sql.sources.schema.part.2' > 'spark.sql.sources.schema.partCol.0' > 'spark.sql.sources.schema.partCol.1' That’s what error seems to say that part1 is defined but part0 is missing.  Solution -  Drop & re-create table. If Table was partitioned  then all partitions  would have been removed. So do either of below -  ·          Msck repair table <db_name>.<table_name> ·    ...
Post a Comment
Read more




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...
Post a Comment
Read more




Read from a hive table and write back to it using spark sql

In context to Spark 2.2 - if we read from an hive table and write to same, we get following exception- scala > dy . write . mode ( "overwrite" ). insertInto ( "incremental.test2" ) org . apache . spark . sql . AnalysisException : Cannot insert overwrite into table that is also being read from .; org . apache . spark . sql . AnalysisException : Cannot insert overwrite into table that is also being read from .; 1. This error means that our process is reading from same table and writing to same table. 2. Normally, this should work as process writes to directory .hiveStaging... 3. This error occurs in case of saveAsTable method, as it overwrites entire table instead of individual partitions. 4. This error should not occur with insertInto method, as it overwrites partitions not the table. 5. A reason why this happening is because Hive table has following Spark TBLProperties in its definition. This problem will solve for insertInto met...
Post a Comment
Read more