**** THIS IS NOT AN OFFICIALLY SUPPORTED DEPLOYMENT METHOD ***** I believe the artifacts that are actually used at runtime are impalad, catalogd, statestored, libfesupport.so, impala-frontend-0.1-SNAPSHOT.jar, impala-data-source-api-1.0-SNAPSHOT.jar, libstdc++.so* libkudu_client.so*
You may be able to get something to work if you replace the versions currently on the cluster with the output from your Impala build. This is a purely experimental method of deployment and may or may not work as expected. If your cluster catches on fire, don't blame me. On Wed, Jun 21, 2017 at 4:03 PM, 孙清孟 <[email protected]> wrote: > Hi Jeszy, > Sorry that I didn't make it clear, I've already installed impala servive > with CM. > I did some modification in Impala, and built it successfully. > now I want to replace the impala installed by CM. > > 2017-06-21 19:29 GMT+08:00 Jeszy <[email protected]>: > > > With CM you can just add Impala as a new service to your cluster. Use > > the dropdown next to the cluster name. A binary version of impala is > > shipped as part of the CDH 5.11 parcels that you have installed. > > > > On 21 June 2017 at 11:58, 孙清孟 <[email protected]> wrote: > > > Hi Tim, > > > I've built Impala according to the describe here: > > > https://cwiki.apache.org/confluence/display/IMPALA/Building+Impala > > > But how can I install the Impala to an already running > > cdh-5.11.0-release > > > cluster that managered by Cloudera Manager. > > > Build Debian packages and use `apt-get`? > > > > > > 2017-06-21 11:16 GMT+08:00 Henry Robinson <[email protected]>: > > > > > >> I don't think there's any plan for this work. The CMake documentation > > would > > >> be where I'd start looking for ideas: > > >> > > >> https://cmake.org/cmake/help/v3.2/command/install.html > > >> > > >> Best, > > >> Henry > > >> > > >> On 20 June 2017 at 18:31, sky <[email protected]> wrote: > > >> > > >> > Hi Tim， > > >> > Is there a plan for this work? Could you provide a manual copy of > > the > > >> > example?Thanks. > > >> > > > >> > > > >> > > > >> > > > >> > > > >> > > > >> > > > >> > > > >> > At 2017-06-21 01:41:33, "Tim Armstrong" <[email protected]> > > wrote: > > >> > >Hi Sky, > > >> > > We have not implemented an install target yet - for deployment we > > rely > > >> > on > > >> > >copying out the artifacts manually. I believe CMake has some > support > > for > > >> > >implementing install targets but nobody has picked up that work > yet. > > >> > > > > >> > >- Tim > > >> > > > > >> > >On Mon, Jun 19, 2017 at 8:45 PM, sky <[email protected]> wrote: > > >> > > > > >> > >> Hi all, > > >> > >> I am using cdh5.11.1-release,the compilation command is > > provided > > >> in > > >> > >> the documentation(./buildall.sh -notests -so),but there is no > > command > > >> > >> similar to 'make install'.In the current document compiled, the > > >> > directory > > >> > >> structure is too much and do not need too many files. Could you > > >> provide > > >> > an > > >> > >> "install" command to extract compiled files to other directories > > for > > >> > easy > > >> > >> management > > >> > > > >> > > >
