A recent project, on the Big Data Transformation Project, the bottom choice Impala or sparksql it?
Finally, choose Impala. This opens up my Impala learning journey. I am responsible for most of the Imapa interface development work.
I am unable to control the whole to understand and learn. All are also tested and studied in the Impala console. The basic command was familiar for almost one or two days.
There is a lot of preparation to be done before development. First of all, we have to build a 500w test data.
Making data in Impala is certainly inconvenient, and all data is created in Oracle. Write stored procedure Run SQL. Data is created in Oracle and will be imported into Impala.
This with contact to Sqoop Import tool, learning really is always learning not to play AH.
。。。 The next step is to toss the data process ... Write interface ... Various tests ...
Do not want to write, the next blog to write some Impala basic Operation command bar. It is mainly used in the work. Have time to stick a small demo out. Convenient for everyone to get started.
What causes contact with Impala