Apache Hive .orig test file and "#### A masked pattern was here ####"


Just a quick information about something in Hive.

If you ever typed:

$ ant clean package test

to run Apache Hive unit tests, you may have seen that Hive sometimes creates two output files.
If you run for example:

$ ant test -Dtestcase=TestCliDriver -Dqfile=alter5.q

Hive sometimes generates a alter5.q.out and a alter5.q.out.orig :

build/ql/test/logs/clientpositive/alter5.q.out
build/ql/test/logs/clientpositive/alter5.q.out.orig

This happens because Hive uses a method to mask any local information, as local time, or local path, with the following sentence:

#### A masked pattern was here ####

So, if you check your .q.out file it should have a bunch of this sentence above covering several local information. This information needs to be covered so that the tests outputs are the same in all computers.

The .q.out.orig file has the original test output, with all the local information non covered.

Out of curiosity, the method to mask the local patterns (private void maskPatterns(String[] patterns, String fname) throws Exception) is located on:

ql/src/test/org/apache/hadoop/hive/ql/QTestUtil.java


Comments

  1. TejutejuApril 17, 2018 at 1:30 AM

    Really Good blog post.provided a helpful information.I hope that you will post more updates like thisHadoop Admin Online Training Bangalore

    ReplyDelete
    Replies
    1. Renata Ghisloti Duarte de Souza GranhaMay 4, 2018 at 8:45 PM

      Thank you so much! I will add soon a post with Hadoop admin tips. :)

      Delete

Post a Comment

Popular posts from this blog

Slope One

Image
Slope One is a simple and efficient type of recommender system. Introduced by Daniel Lemire and Anna Maclachlan in 2005, it involves a simpler idea than the majority of other collaborative filtering implementations. While these usually calculate the similarity between vectors of items using the cosine or the Pearson methods, the Slope One approach recommends items to users based on the average difference in preferences of items.  The main idea of the algorithm is to create a linear relation between items preferences such as the relation F(x) = x + b. The name "Slope One" cames from the fact that here the "x" is multiplied by "1". It basically calculates the difference between the ratings of items for each user (for every item the user has rated). Then, it creates and average difference (diff) for every pair of items. To make a prediction of the Item A for an User 1 for example, it would get the ratings that User 1 has given to other items and a...
Read more

Apache Mahout

Image
“Scalable machine learning library” Mahout is a solid Java framework in the Artificial Intelligence area. It is a machine learning project by the Apache Software Foundation that tries to build intelligent algorithms that learn from some data input. What is special about Mahout is that  it is a scalable library, prepared to deal with huge datasets. Its algorithms are built on top of the Apache Hadoop project and, so, they work with distributed computing. Mahout offers algorithms in three major  areas: Clustering, Categorization and Recommender Systems. This lats part was incoporated in April 4 th 2008, from the previous Taste Recommender System project. Mahout currently implements  a collaborative filtering engine that supports the user-based, item-based and Slope-one recommender systems. Other algorithms available in the package are  the k-means, fuzzy k-Means clustering, Canopy, Dirichlet and Mean-Shift. They also have The Naive Bayes, Complement...
Read more

Error when using smooth.spline

When trying to interpolate a series of data the cubic spline  is a great technique to be used. I choose to use the smooth.spline function, from the R stats package. > smooth.spline(data$x,  data$y ) Nevertheless, while running smooth.spline on a collection of datasets with different sizes I got the following error: Error in smooth.spline( data$x,  data$y),  :   'tol' must be strictly positive and finite After digging a little bit I discovered that the problem was that some datasets were really small and smooth.spline wasn't being able to compute anything. Hence, make sure your dataset is big enough before applying smooth.spline to it. > if(length(data$x) > 30) {  smooth.spline( data$x,  data$y)  } UPDATE:  A more generalized solution would be: > if(IQR(data$x) > 0) {  smooth.spline( data$x,  data$y)  }
Read more