Hi Mahesh, exec - Use the exec command to run a Pig script with no interaction between the script and the Grunt shell (batch mode). Aliases defined in the script are not available to the shell; however, the files produced as the output of the script and stored on the system are visible after the script is run. Aliases defined via the shell are not available to the script. With the exec command, store statements will not trigger execution; rather, the entire script is parsed before execution starts. Unlike the run command, exec does not change the command history or remembers the handles used inside the script. Exec without any parameters can be used in scripts to force execution up to the point in the script where the exec occurs. run command. Both the exec and run commands are useful for debugging because you can modify a Pig script in an editor and then rerun the script in the Grunt shell without leaving the shell. Also, both commands promote Pig script modularity as they allow you to reuse existing components. run - Use the run command to run a Pig script that can interact with the Grunt shell (interactive mode). The script has access to aliases defined externally via the Grunt shell. The Grunt shell has access to aliases defined within the script. All commands from the script are visible in the command history. With the run command, every store triggers execution. The statements from the script are put into the command history and all the aliases defined in the script can be referenced in subsequent statements after the run command has completed. Issuing a run command on the grunt command line has basically the same effect as typing the statements manually. For comparison, see the exec command. Both the run and exec commands are useful for debugging because you can modify a Pig script in an editor and then rerun the script in the Grunt shell without leaving the shell. Also, both commands promote Pig script modularity as they allow you to reuse existing components. For more: https://pig.apache.org/docs/r0.9.1/cmds.html#exec https://pig.apache.org/docs/r0.9.1/cmds.html#run Regards, Karthik Gopal ... View more

Just run the command ambari-server start ... View more

Hi Pranshu, You can follow the instructions in the link below: https://community.hortonworks.com/articles/4427/fix-under-replicated-blocks-in-hdfs-manually.html Regards, Karthik Gopal ... View more

Hi Rushikesh, Hadoop jobs are data intensive, compressing data can speed up the I/O operations - MapReduce jobs are almost always I/O bound Compressed data can save storage space and speed up data transfers across the network - Capital allocation for hardware can go further Reduced I/O and network load can bring significant performance improvements - MapReduce jobs can finish faster overall On the other hand, CPU utilization and processing time increases during compression and decompression - Understanding the tradeoff is important for MapReduce pipeline's overall performance ... View more

Hi Rushikesh, You can create a daily script and use the following option of hadoop fs command to append the an existing file on HDFS. Usage: hadoop fs -appendToFile <localsrc> ... <dst> Append single src, or multiple srcs from local file system to the destination file system. Also reads input from stdin and appends to destination file system. hadoop fs -appendToFile localfile /user/hadoop/hadoopfile hadoop fs -appendToFile localfile1 localfile2 /user/hadoop/hadoopfile hadoop fs -appendToFile localfile hdfs://nn.example.com/hadoop/hadoopfile hadoop fs -appendToFile - hdfs://nn.example.com/hadoop/hadoopfile Reads the input from stdin. Exit Code: Returns 0 on success and 1 on error. ... View more