inside bin folder i executed ./impala-config.sh did u mean it should be
executed from outside of bin folder?

On Tue, Apr 3, 2018 at 1:43 PM, Gabor Kaszab <gaborkas...@cloudera.com>
wrote:

> Well, then you might not source the impala configs properly. Those should
> be set via bin/impala-config.sh. What is the exact command you use for
> sourcing the configs?
>
> On Tue, Apr 3, 2018 at 10:04 AM, Anubhav Tarar <anubhav.ta...@knoldus.in>
> wrote:
>
>> these properties were not set  even after sourcing the configs thats why
>> i export them myself before running the statestore and catalog
>>
>> On Tue, Apr 3, 2018 at 1:25 PM, Gabor Kaszab <gaborkas...@cloudera.com>
>> wrote:
>>
>>> I'm glad that at least the build has been successful eventually :)
>>>
>>> I checked these on my env:
>>> CLUSTER_DIR = <Impala_Home>/testdata/cluster
>>> IMPALA_LLVM_VERSION=3.9.1
>>>
>>> Btw, these should be set properly by impala-config.sh. Is there a reason
>>> you changed these?
>>>
>>>
>>> On Tue, Apr 3, 2018 at 9:27 AM, Anubhav Tarar <anubhav.ta...@knoldus.in>
>>> wrote:
>>>
>>>> yes i do all the steps as you mentioned my impala_home also points to
>>>> right path and build was successful after commenting part of script
>>>>
>>>>  now i am able to query from impala-hiveserver2 successfully i did the
>>>> following extra steps
>>>>
>>>> is anything wrong with these steps?
>>>>
>>>> export CLUSTER_DIR=''/tmp"
>>>> export IMPALA_LLVM_VERSION=2
>>>>
>>>> but only problem is that i can not start impala -shell
>>>>
>>>> this is error
>>>>
>>>> ./impala-shell.sh: line 24: exec: impala-python: not found
>>>>
>>>>
>>>> On Tue, Apr 3, 2018 at 12:38 PM, Gabor Kaszab <gaborkas...@cloudera.com
>>>> > wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I have the feeling that you haven't mentioned all the steps you made.
>>>>> Please next time provide as much information as you have so that we can
>>>>> help easier.
>>>>> As I see you chose "Suggestion 2". These might be silly questions but
>>>>> let's make sure:
>>>>> 1: Did you source the Impala configs?
>>>>> 2: Where does you IMPALA_HOME point to?
>>>>> 3: After commenting that part of the script did you manage to build
>>>>> Impala successfully?
>>>>>
>>>>> My suggestion is to close and re-open your terminal, source the Impala
>>>>> configs, make sure the git part of bootstrap_system.sh is commented, run
>>>>> bootstrap_development.
>>>>> In case all of these succeeded then you can try running
>>>>> start-impala-cluster.sh
>>>>>
>>>>> Gabor
>>>>>
>>>>>
>>>>> On Mon, Apr 2, 2018 at 11:47 AM, Anubhav Tarar <
>>>>> anubhav.ta...@knoldus.in> wrote:
>>>>>
>>>>>> HI,i commented out the part as you said then i try started statestore
>>>>>> but get this exception
>>>>>>
>>>>>> ./start-statestored.sh: line 52: CLUSTER_DIR: unbound variable
>>>>>>
>>>>>> did i need to set these env variables by myself?
>>>>>>
>>>>>> On Thu, Mar 29, 2018 at 7:41 PM, Gabor Kaszab <
>>>>>> gaborkas...@cloudera.com> wrote:
>>>>>>
>>>>>>> That can be an issue because the build is being executed in ~/Impala
>>>>>>> according your logs you pasted even though you tried to build it in a
>>>>>>> different directory.
>>>>>>>
>>>>>>> Suggestion 1:
>>>>>>> My suggestion is (in case you don't insist to the Impala dir you
>>>>>>> created on your own) is the following:
>>>>>>> 1: Close you console and re-open a new one.
>>>>>>> 2: Move to /home/anubhav/Impala
>>>>>>> 3: Make the config sourcing in this dir
>>>>>>> 4: bootstrap_development.sh
>>>>>>>
>>>>>>> The thing is that bootstrap_development.sh for some reason does a
>>>>>>> git clone to ~/Impala and tries to build there, and if you have done 
>>>>>>> your
>>>>>>> config sourcing in another directory that that can cause some issues.
>>>>>>> (Haven't tried to compile in ~/Impala, though, I always went for 
>>>>>>> Suggestion
>>>>>>> 2)
>>>>>>>
>>>>>>> Suggestion 2:
>>>>>>> In case you insist to building Impala in the directory where you
>>>>>>> have extracted the source files then it's a bit trickier: The only way I
>>>>>>> found to do so with bootstrap_development.sh is to comment out the part
>>>>>>> from the code that does the git clone from bootstrap_system.sh.
>>>>>>> Basically this part should be commented:
>>>>>>> "
>>>>>>>
>>>>>>> if ! [[ -d ~/Impala ]]
>>>>>>>
>>>>>>> then
>>>>>>>
>>>>>>>   time -p git clone https://git-wip-us.apache.org/repos/asf/impala.
>>>>>>> git ~/Impala
>>>>>>>
>>>>>>> fi
>>>>>>>
>>>>>>> cd ~/Impala
>>>>>>> "
>>>>>>> Well, it might be enough to comment out the cd ~/Impala part.
>>>>>>>
>>>>>>> Hope this helps.
>>>>>>> Gabor
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Thu, Mar 29, 2018 at 3:52 PM, Anubhav Tarar <
>>>>>>> anubhav.ta...@knoldus.in> wrote:
>>>>>>>
>>>>>>>> No I am not executing step3 from /user/Anubhav/impala I am
>>>>>>>> executing it from folder where I downloaded binary impala
>>>>>>>> On 29-Mar-2018 6:56 PM, "Gabor Kaszab" <gaborkas...@cloudera.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Thx for collecting these details.
>>>>>>>>>
>>>>>>>>> 1:
>>>>>>>>> Do your step 4 (source configs) before step 3
>>>>>>>>> (bootstrap_development.sh)
>>>>>>>>>
>>>>>>>>> 2:
>>>>>>>>> Are you executing step 3 from /home/anubhav/Impala?
>>>>>>>>>
>>>>>>>>> 3:
>>>>>>>>> If your build is still failing after doing 1: could you search for
>>>>>>>>> the particular error in the command's output? There might be something
>>>>>>>>> useful because the last few lines you copied aren't that useful to be
>>>>>>>>> honest.
>>>>>>>>>
>>>>>>>>> 4:
>>>>>>>>> If your Impala build fails in your step3 then there is no point
>>>>>>>>> doing step5.
>>>>>>>>>
>>>>>>>>> Gabor
>>>>>>>>>
>>>>>>>>> On Thu, Mar 29, 2018 at 1:29 PM, Anubhav Tarar <
>>>>>>>>> anubhav.ta...@knoldus.in> wrote:
>>>>>>>>>
>>>>>>>>>> HI,Here are the steps
>>>>>>>>>>
>>>>>>>>>> step 1.download impala 2.11 from official download page
>>>>>>>>>> step 2.extract he jar
>>>>>>>>>> step 3.goes to impala folder and hit command
>>>>>>>>>>
>>>>>>>>>> bootstrap_development.sh
>>>>>>>>>>
>>>>>>>>>> which give this output
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> [INFO] BUILD SUCCESS
>>>>>>>>>> [ 86%] Built target fe
>>>>>>>>>> Makefile:94: recipe for target 'all' failed
>>>>>>>>>> make: *** [all] Error 2
>>>>>>>>>> Error in /home/anubhav/Impala/bin/make_impala.sh at line 178:
>>>>>>>>>> ${MAKE_CMD} ${MAKE_ARGS}
>>>>>>>>>>
>>>>>>>>>> step 4: source the configs
>>>>>>>>>>
>>>>>>>>>> ./bin/impala-config.sh;
>>>>>>>>>>
>>>>>>>>>> . /bin/set-pythonpath.sh;
>>>>>>>>>>
>>>>>>>>>> . /bin/set-classpath.sh
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> step 5: start the impalad
>>>>>>>>>>
>>>>>>>>>> ./start-impala-cluster.py
>>>>>>>>>> /usr/bin/env: ‘impala-python’: No such file or directory
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> I am trying as much as i can but these  problems are not on
>>>>>>>>>> google and impala documentation doesn't seems to provide much help in
>>>>>>>>>> comparison to hive or presto
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Thu, Mar 29, 2018 at 4:30 PM, Jeszy <jes...@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hello Anubhav,
>>>>>>>>>>>
>>>>>>>>>>> Please include the steps that you've tried on your own to
>>>>>>>>>>> resolve this
>>>>>>>>>>> problem, the blockers you've faced, and in general provide as
>>>>>>>>>>> much
>>>>>>>>>>> information as possible about the problem at hand to encourage
>>>>>>>>>>> community members to spend time of their own working with you.
>>>>>>>>>>> Answering the questions you were asked earlier is the least, but
>>>>>>>>>>> I'd
>>>>>>>>>>> strongly encourage you to try to make sense of the error
>>>>>>>>>>> messages and
>>>>>>>>>>> attempt to take the issue as far as you can by reading Impala's
>>>>>>>>>>> wiki
>>>>>>>>>>> pages and searching online.
>>>>>>>>>>>
>>>>>>>>>>> HTH
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On 29 March 2018 at 12:36, Anubhav Tarar <
>>>>>>>>>>> anubhav.ta...@knoldus.in> wrote:
>>>>>>>>>>> > i resolved all your points but when i hit he development
>>>>>>>>>>> script this is the
>>>>>>>>>>> > error when i hit bootstrap
>>>>>>>>>>> > _development.sh
>>>>>>>>>>> >
>>>>>>>>>>> > [INFO] BUILD SUCCESS
>>>>>>>>>>> > [ 86%] Built target fe
>>>>>>>>>>> > Makefile:94: recipe for target 'all' failed
>>>>>>>>>>> > make: *** [all] Error 2
>>>>>>>>>>> > Error in /home/anubhav/Impala/bin/make_impala.sh at line 178:
>>>>>>>>>>> ${MAKE_CMD}
>>>>>>>>>>> > ${MAKE_ARGS}
>>>>>>>>>>> >
>>>>>>>>>>> > now when i tried to run my impalad this is the error
>>>>>>>>>>> >
>>>>>>>>>>> > anubhav@anubhav-Vostro-3559:~/Impala/bin$ ./start-impalad.sh
>>>>>>>>>>> > ./start-impalad.sh: line 89: /admin: No such file or directory
>>>>>>>>>>> > /home/anubhav/Impala/be/build/latest/service/impalad: error
>>>>>>>>>>> while loading
>>>>>>>>>>> > shared libraries: libjvm.so: cannot open shared object file:
>>>>>>>>>>> No such file or
>>>>>>>>>>> > directory
>>>>>>>>>>> >
>>>>>>>>>>> >
>>>>>>>>>>> > someone please help
>>>>>>>>>>> >
>>>>>>>>>>> > On Wed, Mar 28, 2018 at 8:21 PM, Gabor Kaszab <
>>>>>>>>>>> gaborkas...@cloudera.com>
>>>>>>>>>>> > wrote:
>>>>>>>>>>> >>
>>>>>>>>>>> >> I few questions:
>>>>>>>>>>> >> - Is /home/anubhav/Impala the directory you expect your
>>>>>>>>>>> Impala sources.
>>>>>>>>>>> >> (It can happen that bootstrap_development.sh check-out Impala
>>>>>>>>>>> to a different
>>>>>>>>>>> >> directory you'd expect)
>>>>>>>>>>> >> - Can you find that kudu/client/client.h file somewhere in
>>>>>>>>>>> you toolchain
>>>>>>>>>>> >> directory? (To rule out that the script searches it on a
>>>>>>>>>>> wrong path)
>>>>>>>>>>> >> - Do you have a toolchain directory at all?
>>>>>>>>>>> >> - Have you executed those commands I sent you to set env
>>>>>>>>>>> variables?
>>>>>>>>>>> >>
>>>>>>>>>>> >> Gabor
>>>>>>>>>>> >>
>>>>>>>>>>> >> On Wed, Mar 28, 2018 at 8:23 AM, Anubhav Tarar <
>>>>>>>>>>> anubhav.ta...@knoldus.in>
>>>>>>>>>>> >> wrote:
>>>>>>>>>>> >>>
>>>>>>>>>>> >>> hi i cloned the apache impala then hit command
>>>>>>>>>>> >>> ./bin/bootstrap_development.sh
>>>>>>>>>>> >>>
>>>>>>>>>>> >>> still getting the same error
>>>>>>>>>>> >>>
>>>>>>>>>>> >>>   File 
>>>>>>>>>>> >>> "/home/anubhav/Impala/infra/python/bootstrap_virtualenv.py",
>>>>>>>>>>> line
>>>>>>>>>>> >>> 379, in <module>
>>>>>>>>>>> >>>     kudu_client_dir = find_kudu_client_install_dir()
>>>>>>>>>>> >>>   File 
>>>>>>>>>>> >>> "/home/anubhav/Impala/infra/python/bootstrap_virtualenv.py",
>>>>>>>>>>> line
>>>>>>>>>>> >>> 315, in find_kudu_client_install_dir
>>>>>>>>>>> >>>     error_if_kudu_client_not_found(install_dir)
>>>>>>>>>>> >>>   File 
>>>>>>>>>>> >>> "/home/anubhav/Impala/infra/python/bootstrap_virtualenv.py",
>>>>>>>>>>> line
>>>>>>>>>>> >>> 322, in error_if_kudu_client_not_found
>>>>>>>>>>> >>>     raise Exception("Kudu client header not found at %s" %
>>>>>>>>>>> header_path)
>>>>>>>>>>> >>> Exception: Kudu client header not found at
>>>>>>>>>>> >>> /home/anubhav/Impala/toolchain/kudu-0eef8e0/debug/include/ku
>>>>>>>>>>> du/client/client.h
>>>>>>>>>>> >>> Error in /home/anubhav/Impala/bin/impala-python at line 25:
>>>>>>>>>>> >>>
>>>>>>>>>>> >>>
>>>>>>>>>>> >>> On Tue, Mar 27, 2018 at 1:48 PM, Jeszy <jes...@gmail.com>
>>>>>>>>>>> wrote:
>>>>>>>>>>> >>>>
>>>>>>>>>>> >>>> Hello Anubhav,
>>>>>>>>>>> >>>>
>>>>>>>>>>> >>>> Impala doesn't ship it's releases in binary format, so you
>>>>>>>>>>> will have
>>>>>>>>>>> >>>> to build it locally after downloading the source. For
>>>>>>>>>>> instruction on
>>>>>>>>>>> >>>> how to do that, see Gabor's comments.
>>>>>>>>>>> >>>>
>>>>>>>>>>> >>>> If you don't have an existing Hadoop cluster on which you
>>>>>>>>>>> want to run
>>>>>>>>>>> >>>> Impala, you can just use one of the distributor's packaged
>>>>>>>>>>> (binary)
>>>>>>>>>>> >>>> versions. Cloudera's CDH is also open source.
>>>>>>>>>>> >>>>
>>>>>>>>>>> >>>> HTH
>>>>>>>>>>> >>>>
>>>>>>>>>>> >>>> On 27 March 2018 at 10:14, Gabor Kaszab <
>>>>>>>>>>> gaborkas...@cloudera.com>
>>>>>>>>>>> >>>> wrote:
>>>>>>>>>>> >>>> > I have already provided you the sourcing steps in my
>>>>>>>>>>> first mail:
>>>>>>>>>>> >>>> > "Also, did you source the Impala configs? These are the
>>>>>>>>>>> ones I usually
>>>>>>>>>>> >>>> > use:
>>>>>>>>>>> >>>> >
>>>>>>>>>>> >>>> > . bin/impala-config.sh;
>>>>>>>>>>> >>>> >
>>>>>>>>>>> >>>> > . bin/set-pythonpath.sh;
>>>>>>>>>>> >>>> >
>>>>>>>>>>> >>>> > . bin/set-classpath.sh
>>>>>>>>>>> >>>> >
>>>>>>>>>>> >>>> > "
>>>>>>>>>>> >>>> >
>>>>>>>>>>> >>>> >
>>>>>>>>>>> >>>> > Have you tried following the Impala build page?
>>>>>>>>>>> >>>> >
>>>>>>>>>>> >>>> > https://cwiki.apache.org/confl
>>>>>>>>>>> uence/display/IMPALA/Building+Impala
>>>>>>>>>>> >>>> >
>>>>>>>>>>> >>>> >
>>>>>>>>>>> >>>> > Gabor
>>>>>>>>>>> >>>> >
>>>>>>>>>>> >>>> >
>>>>>>>>>>> >>>> >
>>>>>>>>>>> >>>> > On Tue, Mar 27, 2018 at 10:08 AM, Anubhav Tarar
>>>>>>>>>>> >>>> > <anubhav.ta...@knoldus.in>
>>>>>>>>>>> >>>> > wrote:
>>>>>>>>>>> >>>> >>
>>>>>>>>>>> >>>> >> i didn't clone the open source i downloaded apache
>>>>>>>>>>> impala 2.11
>>>>>>>>>>> >>>> >> release
>>>>>>>>>>> >>>> >> from download page of official documentation
>>>>>>>>>>> >>>> >> https://impala.apache.org/downloads.html and what do
>>>>>>>>>>> you mean by
>>>>>>>>>>> >>>> >> sourcing of
>>>>>>>>>>> >>>> >> configs what are the steps? can you please provide me
>>>>>>>>>>> complete steps
>>>>>>>>>>> >>>> >> i am
>>>>>>>>>>> >>>> >> struck from 2 days
>>>>>>>>>>> >>>> >
>>>>>>>>>>> >>>> >
>>>>>>>>>>> >>>
>>>>>>>>>>> >>>
>>>>>>>>>>> >>>
>>>>>>>>>>> >>>
>>>>>>>>>>> >>> --
>>>>>>>>>>> >>> Thanks and Regards
>>>>>>>>>>> >>>             Anubhav Tarar
>>>>>>>>>>> >>>
>>>>>>>>>>> >>>  Software Consultant
>>>>>>>>>>> >>>       Knoldus Software LLP
>>>>>>>>>>> >>>        LinkedIn     Twitter    fb
>>>>>>>>>>> >>>           mob : 8588915184 <(858)%20891-5184>
>>>>>>>>>>> >>
>>>>>>>>>>> >>
>>>>>>>>>>> >
>>>>>>>>>>> >
>>>>>>>>>>> >
>>>>>>>>>>> > --
>>>>>>>>>>> > Thanks and Regards
>>>>>>>>>>> >             Anubhav Tarar
>>>>>>>>>>> >
>>>>>>>>>>> >  Software Consultant
>>>>>>>>>>> >       Knoldus Software LLP
>>>>>>>>>>> >        LinkedIn     Twitter    fb
>>>>>>>>>>> >           mob : 8588915184 <(858)%20891-5184>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Thanks and Regards
>>>>>>>>>>
>>>>>>>>>> *   Anubhav Tarar     *
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> * Software Consultant*
>>>>>>>>>>       *Knoldus Software LLP <http://www.knoldus.com/home.knol>
>>>>>>>>>>      *
>>>>>>>>>>        LinkedIn <http://in.linkedin.com/in/rahulforallp>
>>>>>>>>>> Twitter <https://twitter.com/RahulKu71223673>    fb
>>>>>>>>>> <rahulfora...@facebook.com>
>>>>>>>>>>           mob : 8588915184 <(858)%20891-5184>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Thanks and Regards
>>>>>>
>>>>>> *   Anubhav Tarar     *
>>>>>>
>>>>>>
>>>>>> * Software Consultant*
>>>>>>       *Knoldus Software LLP <http://www.knoldus.com/home.knol>
>>>>>>  *
>>>>>>        LinkedIn <http://in.linkedin.com/in/rahulforallp>     Twitter
>>>>>> <https://twitter.com/RahulKu71223673>    fb
>>>>>> <rahulfora...@facebook.com>
>>>>>>           mob : 8588915184 <(858)%20891-5184>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Thanks and Regards
>>>>
>>>> *   Anubhav Tarar     *
>>>>
>>>>
>>>> * Software Consultant*
>>>>       *Knoldus Software LLP <http://www.knoldus.com/home.knol>       *
>>>>        LinkedIn <http://in.linkedin.com/in/rahulforallp>     Twitter
>>>> <https://twitter.com/RahulKu71223673>    fb <rahulfora...@facebook.com>
>>>>
>>>>           mob : 8588915184 <(858)%20891-5184>
>>>>
>>>
>>>
>>
>>
>> --
>> Thanks and Regards
>>
>> *   Anubhav Tarar     *
>>
>>
>> * Software Consultant*
>>       *Knoldus Software LLP <http://www.knoldus.com/home.knol>       *
>>        LinkedIn <http://in.linkedin.com/in/rahulforallp>     Twitter
>> <https://twitter.com/RahulKu71223673>    fb <rahulfora...@facebook.com>
>>           mob : 8588915184 <(858)%20891-5184>
>>
>
>


-- 
Thanks and Regards

*   Anubhav Tarar     *


* Software Consultant*
      *Knoldus Software LLP <http://www.knoldus.com/home.knol>       *
       LinkedIn <http://in.linkedin.com/in/rahulforallp>     Twitter
<https://twitter.com/RahulKu71223673>    fb <rahulfora...@facebook.com>
          mob : 8588915184

Reply via email to