Re: Welcome Fredy Wijaya to Impala PMC

[Fredy Wijaya]

On 2019/07/29 17:33:02, Xiaomeng Zhang  wrote: 
> Congrats Fredy!
> 
> On Mon, Jul 29, 2019 at 10:19 AM David Knupp  wrote:
> 
> > Congratulations Fredy!
> >
> > On Mon, Jul 29, 2019 at 10:10 AM Sahil Takiar 
> > wrote:
> >
> > > Congrats Fredy!
> > >
> > > On Mon, Jul 29, 2019 at 10:03 AM Vihang Karajgaonkar <
> > vih...@cloudera.com>
> > > wrote:
> > >
> > > > Congratulations Fredy!
> > > >
> > > > On Sun, Jul 28, 2019 at 10:14 PM Quanlong Huang <
> > huangquanl...@gmail.com
> > > >
> > > > wrote:
> > > >
> > > > > Congratulations!
> > > > >
> > > > > On Sun, Jul 28, 2019 at 11:48 AM Andrew Sherman <
> > asher...@cloudera.com
> > > >
> > > > > wrote:
> > > > >
> > > > > > Congratulations Fredy!
> > > > > >
> > > > > > On Sun, Jul 28, 2019 at 10:05 AM Bharath Vissapragada <
> > > > > bhara...@apache.org
> > > > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > The Project Management Committee (PMC) for Apache Impala has
> > > invited
> > > > > > Fredy
> > > > > > > Wijaya to become a PMC member and we are pleased to announce that
> > > > they
> > > > > > have
> > > > > > > accepted.
> > > > > > >
> > > > > > > Congratulations and welcome, Fredy.
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > >
> > > --
> > > Sahil Takiar
> > > Software Engineer
> > > takiar.sa...@gmail.com | (510) 673-0309
> > >
> >
> >
> > --
> > David Knupp | Software Engineer
> > Cloudera Inc., 525 Market Street #3100. San Francisco, CA 94105
> >
> Thanks everyone!

Re: New Committer: Laszlo Gaal

[Fredy Wijaya]

Congrats, Laszlo!

On Wed, Jun 19, 2019 at 11:45 AM Zoltán Borók-Nagy 
wrote:

> Congrats, Laszlo!
>
> On Wed, Jun 19, 2019 at 6:34 PM Jeszy  wrote:
>
> > Congrats Laszlo!
> >
> > On Wed, Jun 19, 2019 at 12:31 PM Andrew Sherman 
> > wrote:
> > >
> > > Congratulations Laszlo, good news just before your PTO!
> > >
> > > On Wed, Jun 19, 2019 at 9:30 AM Lars Volker  wrote:
> > >
> > > > Hi All,
> > > >
> > > > The Project Management Committee (PMC) for Apache Impala
> > > > has invited Laszlo Gaal to become a committer and we are pleased
> > > > to announce that he has accepted.
> > > >
> > > > Welcome and congratulations, Laszlo!
> > > >
> >
>

Re: New Committer - Andrew Sherman

[Fredy Wijaya]

Congrats!

On Fri, Jun 7, 2019 at 1:33 PM Bikramjeet Vig 
wrote:

> Congratulations Andrew !
>
> On Fri, Jun 7, 2019 at 11:22 AM Thomas Tauber-Marshall <
> tmarsh...@cloudera.com> wrote:
>
> > Hi All,
> >
> > The Project Management Committee (PMC) for Apache Impala
> > has invited Andrew Sherman to become a committer and we are pleased
> > to announce that he has accepted.
> >
> > Welcome and congratulations, Andrew!
> >
>

Re: New PMC Members: Gabor Kaszab and Bikramjeet Vig

[Fredy Wijaya]

Congrats!

On Fri, May 31, 2019 at 11:28 AM Joe McDonnell 
wrote:

> Congrats to both of you!
>
> On Fri, May 31, 2019 at 9:27 AM David Knupp  wrote:
>
> > Congratulations, and well deserved!
> >
> > On Fri, May 31, 2019 at 6:30 AM Gabor Kaszab 
> > wrote:
> >
> > > Thanks everyone! :)
> > > Gabor
> > >
> > > On Fri, May 31, 2019 at 1:06 PM Csaba Ringhofer <
> > csringho...@cloudera.com>
> > > wrote:
> > >
> > > > Congratulations!
> > > >
> > > > On Fri, May 31, 2019 at 12:09 PM Zoltán Borók-Nagy <
> > > > borokna...@cloudera.com>
> > > > wrote:
> > > >
> > > > > Congrats, well done!
> > > > >
> > > > > On Fri, May 31, 2019 at 11:32 AM Laszlo Gaal <
> > laszlo.g...@cloudera.com
> > > >
> > > > > wrote:
> > > > >
> > > > > > Congrats to both of you!
> > > > > >
> > > > > > On Fri, May 31, 2019 at 6:24 AM Quanlong Huang <
> > > > huangquanl...@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Congratulations!
> > > > > > >
> > > > > > > On Fri, May 31, 2019 at 10:57 AM Andrew Sherman <
> > > > asher...@cloudera.com
> > > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Well done!
> > > > > > > >
> > > > > > > > On Thu, May 30, 2019 at 7:52 PM Vihang Karajgaonkar <
> > > > > > vih...@cloudera.com
> > > > > > > >
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Congratulations Gabor and Bikram!
> > > > > > > > >
> > > > > > > > > On Thu, May 30, 2019 at 6:29 PM Yuneng Fan <
> > a...@cloudera.com>
> > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Congratulations Gabor and Bikram!
> > > > > > > > > >
> > > > > > > > > > On Thu, May 30, 2019 at 5:39 PM Xiaomeng Zhang <
> > > > > > > xiaom...@cloudera.com>
> > > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Wow! Congrats Gabor and Bikram!
> > > > > > > > > > >
> > > > > > > > > > > On Thu, May 30, 2019 at 5:25 PM Lars Volker <
> > > l...@cloudera.com
> > > > >
> > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > > The Project Management Committee (PMC) for Apache
> > Impala
> > > > has
> > > > > > > > invited
> > > > > > > > > > > > Gabor Kaszab and Bikramjeet Vig to become PMC members
> > and
> > > > we
> > > > > > are
> > > > > > > > > > pleased
> > > > > > > > > > > to
> > > > > > > > > > > > announce
> > > > > > > > > > > > that they have accepted.
> > > > > > > > > > > >
> > > > > > > > > > > > Congratulations and welcome, Gabor and Bikram!
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> >
> > --
> > David Knupp | Software Engineer
> > Cloudera Inc., 525 Market Street #3100. San Francisco, CA 94105
> >
>

Re: New Committer: Sahil Takiar

[Fredy Wijaya]

Congrats!

On Wed, May 22, 2019 at 10:20 AM Joe McDonnell 
wrote:

> Congrats!
>
> On Wed, May 22, 2019 at 8:11 AM Laszlo Gaal 
> wrote:
>
> > Congrats, Sahil!
> >
> > On Wed, May 22, 2019 at 4:56 PM David Rorke  wrote:
> >
> > > Congratulations Sahil!
> > >
> > > On Wed, May 22, 2019 at 6:24 AM Andrew Sherman 
> > > wrote:
> > >
> > > > Congratulations Sahil!
> > > >
> > > >
> > > > On Tue, May 21, 2019 at 11:37 PM Lars Volker 
> wrote:
> > > >
> > > > > Hi All,
> > > > >
> > > > > The Project Management Committee (PMC) for Apache Impala
> > > > > has invited Sahil Takiar to become a committer and we are pleased
> > > > > to announce that he has accepted.
> > > > >
> > > > > Welcome and congratulations, Sahil!
> > > > >
> > > >
> > >
> >
>

Re: New committer - Vihang Karajgaonkar

[Fredy Wijaya]

Congratulations, Vihang!

On Tue, May 14, 2019 at 4:12 PM Tim Armstrong 
wrote:

> The Project Management Committee (PMC) for Apache Impala has invited Vihang
> Karajgaonkar to become a committer and we are pleased to announce that they
> have accepted.
> Congratulations and welcome, Vihang!
>

Re: ub1604 from scratch job major run time increase?

[Fredy Wijaya]

One culprit will be the Ranger authorization tests in AuthorizationStmtTest
since we now run the tests against both Sentry and Ranger:
https://github.com/apache/impala/blob/931a8f0ba7f45d5b1608e62aff397b517b943e95/fe/src/test/java/org/apache/impala/analysis/AuthorizationStmtTest.java#L171-L174.
However, this gives us a good coverage and also ensures similar behavior
between Sentry and Ranger. I hope this is a good trade off.

On Mon, Apr 29, 2019 at 10:32 AM Tim Armstrong 
wrote:

> It looks like 30 minutes is somehow lost in frontend tests:
>
>
> *02:20:56* [INFO] Tests run: 10, Failures: 0, Errors: 0, Skipped: 0,
> Time elapsed: 7.156 s - in
> org.apache.impala.authorization.sentry.SentryProxyTest*02:20:56*
> [INFO] Running org.apache.impala.catalog.CatalogTest*02:52:05* [INFO]
> Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.749
> s - in org.apache.impala.catalog.CatalogTest*02:52:05* [INFO] Running
> org.apache.impala.catalog.CatalogObjectToFromThriftTest*02:52:05*
> [INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
> 0.736 s - in
> org.apache.impala.catalog.CatalogObjectToFromThriftTest*02:52:05*
> [INFO] Running
> org.apache.impala.catalog.events.MetastoreEventsProcessorTest*02:52:05*
> [INFO] Tests run: 30, Failures: 0, Errors: 0, Skipped: 0, Time
> elapsed: 187.46 s - in
> org.apache.impala.catalog.events.MetastoreEventsProcessorTest
>
>
> I'm not sure where the other increase is coming from - may just be organic
> growth in the number of tests and we need to cut down runtime elsewhere.
>
> On Sun, Apr 28, 2019 at 11:17 AM Jim Apple  wrote:
>
> > The major from-scratch job in the pre-merge tests seems to frequently be
> > taking more than 5 hours. It used to frequently take less than 4, as of a
> > month or two ago.
> >
> > Here's a job that calls that, to show how long the job has been taking
> > recently:
> >
> >
> https://jenkins.impala.io/view/Utility/job/parallel-all-tests/buildTimeTrend
> >
> > Was something big added that increased the run time? It's possible I
> missed
> > an email thread about this.
> >
>

Impala-lzo Build Error

[Fredy Wijaya]

In case you hit an error like this when building Impala from the HEAD,
update Impala-lzo repo by pulling it from the master.

In file included from
/home/fwijaya/Impala/be/src/util/collection-metrics.h:22:0,
 from /home/fwijaya/Impala/be/src/runtime/tmp-file-mgr.h:31,
 from
/home/fwijaya/Impala/be/src/runtime/bufferpool/buffer-pool.h:33,
 from
/home/fwijaya/Impala/be/src/runtime/runtime-filter-bank.h:23,
 from
/home/fwijaya/Impala/be/src/runtime/runtime-filter.h:23,
 from /home/fwijaya/Impala/be/src/exec/filter-context.h:24,
 from
/home/fwijaya/Impala/be/src/exec/hdfs-scan-node-base.h:31,
 from /home/fwijaya/Impala/be/src/exec/hdfs-scanner.h:31,
 from
/home/fwijaya/Impala/be/src/exec/hdfs-text-scanner.h:22,
 from /home/fwijaya/Impala-lzo/hdfs-lzo-text-scanner.h:9,
 from /home/fwijaya/Impala-lzo/hdfs-lzo-text-scanner.cc:22:
/home/fwijaya/Impala/be/src/util/metrics.h:29:49: fatal error:
gtest/gtest_prod.h: No such file or directory
 #include  // for FRIEND_TEST
 ^
compilation terminated.
CMakeFiles/impalalzo.dir/build.make:62: recipe for target
'CMakeFiles/impalalzo.dir/hdfs-lzo-text-scanner.cc.o' failed
make[6]: *** [CMakeFiles/impalalzo.dir/hdfs-lzo-text-scanner.cc.o] Error 1
CMakeFiles/Makefile2:67: recipe for target 'CMakeFiles/impalalzo.dir/all'
failed
make[5]: *** [CMakeFiles/impalalzo.dir/all] Error 2
Makefile:83: recipe for target 'all' failed
make[4]: *** [all] Error 2
Error in ../Impala-lzo/build.sh at line 38: "${MAKE_CMD:-make}"
CMakeFiles/impala-lzo.dir/build.make:57: recipe for target
'CMakeFiles/impala-lzo' failed
make[3]: *** [CMakeFiles/impala-lzo] Error 2
CMakeFiles/Makefile2:67: recipe for target 'CMakeFiles/impala-lzo.dir/all'
failed
make[2]: *** [CMakeFiles/impala-lzo.dir/all] Error 2
CMakeFiles/Makefile2:79: recipe for target 'CMakeFiles/impala-lzo.dir/rule'
failed
make[1]: *** [CMakeFiles/impala-lzo.dir/rule] Error 2
Makefile:129: recipe for target 'impala-lzo' failed
make: *** [impala-lzo] Error 2

Re: New committer - Pooja Nilangekar

[Fredy Wijaya]

Congrats Pooja!

On Mon, Apr 15, 2019 at 11:18 AM Laszlo Gaal 
wrote:

> Congrats Pooja and welcome!
>
> On Mon, Apr 15, 2019 at 6:17 PM Bharathkrishna Guruvayoor Murali <
> bhar...@cloudera.com> wrote:
>
> > Congratulations Pooja ! :-)
> >
> > On Mon, Apr 15, 2019, 09:11 Bikramjeet Vig 
> > wrote:
> >
> > > Congratulations Pooja!
> > >
> > > On Sat, Apr 13, 2019 at 8:59 AM Tim Armstrong  >
> > > wrote:
> > >
> > > >  The Project Management Committee (PMC) for Apache Impala has invited
> > > > Pooja Nilangekar to become a committer and we are pleased to announce
> > > that
> > > > they have accepted.
> > > > Congratulations and welcome, Pooja!
> > > >
> > >
> >
>

Re: New PMC member: Quanlong Huang

[Fredy Wijaya]

Congratulations Quanlong!

On Mon, Mar 11, 2019 at 8:53 AM Quanlong Huang 
wrote:

> Thanks you, friends! It's my honor to take more responsibility and serve
> more to the community!
>
> On Mon, Mar 11, 2019 at 9:20 PM Zoltán Borók-Nagy  >
> wrote:
>
> > Congrats!
> >
> >
> > On Mon, Mar 11, 2019 at 9:33 AM Gabor Kaszab 
> > wrote:
> >
> > > Congrats!
> > >
> > > On Mon, Mar 11, 2019 at 9:23 AM Jeszy  wrote:
> > >
> > > > Congrats Quanlong!
> > > >
> > > > On Mon, Mar 11, 2019 at 7:57 AM Jim Apple 
> > wrote:
> > > > >
> > > > > The Project Management Committee (PMC) for Apache Impala has
> invited
> > > > > Quanlong Huang to become a PMC member and we are pleased to
> announce
> > > > > that they have accepted.
> > > > >
> > > > > Congratulations and welcome, Quanlong!
> > > >
> > >
> >
>

Ranger Error after Rebasing

[Fredy Wijaya]

Hello,

In case you are getting an error after rebasing due to some commits related
to Ranger, please do the full build: ./buildall.sh -format -testdata
-notests

An example of an error:
--> Starting Ranger Server
find:
'/home/foo/src/Impala/toolchain/ranger-1.2.0-admin/ews/webapp/WEB-INF/classes/conf/':
No such file or directory
mkdir: cannot create directory '/var/run/ranger': Permission denied
chmod: cannot access '/var/run/ranger': No such file or directory
Restarting Apache Ranger Admin
Apache Ranger Admin Service is not running
Starting Apache Ranger Admin Service
/home/philip/src/Impala/toolchain/ranger-1.2.0-admin/ews/ranger-admin-services.sh:
line 85:
/home/foo/src/Impala/toolchain/ranger-1.2.0-admin/ews/logs/catalina.out: No
such file or directory
Apache Ranger Admin Service failed to start!

In case you want a quicker way without rebuilding everything, the following
steps should do the trick.

$IMPALA_HOME/bin/create-test-configuration.sh -create_ranger_policy_db
$IMPALA_HOME/testdata/bin/run-all.sh

I apologize for the inconvenience and please let me know if you encounter
an issue.

Re: Build failed at branch-2.x again

[Fredy Wijaya]

Hi Quanlong,

I created a JIRA for that: https://issues.apache.org/jira/browse/IMPALA-7922
CR is here: https://gerrit.cloudera.org/c/12027/

On Mon, Dec 3, 2018 at 3:07 AM Quanlong Huang 
wrote:

> Hi all,
>
> I encountered a maven failure while building branch-2.x:
>
> *Scanning dependencies of target yarn-extras*
>
> 
>
> Running mvn  -B install -DskipTests
>
> Directory /mnt/volume1/impala-orc/incubator-impala/common/yarn-extras
>
> 
>
> [WARNING] Could not transfer metadata
> com.cloudera.cdh:cdh-root:5.16.0-SNAPSHOT/maven-metadata.xml from/to
> ${distMgmtSnapshotsId} (${distMgmtSnapshotsUrl}): No connector available to
> access repository ${distMgmtSnapshotsId} (${distMgmtSnapshotsUrl}) of type
> default using the available factories WagonRepositoryConnectorFactory
>
> [INFO] BUILD FAILURE
>
> [ERROR] Failed to execute goal on project yarn-extras: Could not resolve
> dependencies for project org.apache.impala:yarn-extras:jar:0.1-SNAPSHOT:
> Failed to collect dependencies for
> [org.apache.hadoop:hadoop-common:jar:2.6.0-cdh5.16.0-SNAPSHOT (compile),
> org.apache.hadoop:hadoop-yarn-api:jar:2.6.0-cdh5.16.0-SNAPSHOT (compile),
> org.apache.hadoop:hadoop-yarn-common:jar:2.6.0-cdh5.16.0-SNAPSHOT
> (compile)]: Failed to read artifact descriptor for
>
> org.codehaus.jackson:jackson-mapper-asl:jar:${cdh.jackson-mapper-asl.version}:
> Could not transfer artifact
>
> org.codehaus.jackson:jackson-mapper-asl:pom:${cdh.jackson-mapper-asl.version}
> from/to cdh.rcs.releases.repo (
> https://repository.cloudera.com/content/groups/cdh-releases-rcs): Illegal
> character in path at index 105:
>
> https://repository.cloudera.com/content/groups/cdh-releases-rcs/org/codehaus/jackson/jackson-mapper-asl/${cdh.jackson-mapper-asl.version}/jackson-mapper-asl-${cdh.jackson-mapper-asl.version}.pom
> -> [Help 1]
>
> [ERROR]
>
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
>
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>
> [ERROR]
>
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
>
> [ERROR] [Help 1]
>
> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
>
> It looks like some changes in cdh-5.16.0-SNAPSHOT jars break this. Shame on
> me that still using the 2.x version... Would be really appreciated if
> anyone can help to have a look.
>
> Thanks,
> Quanlong
>

Re: Issues launching gerrit-verify-dry-run job?

[Fredy Wijaya]

Same issue here.

On Mon, Oct 15, 2018 at 3:24 PM Bharath Vissapragada 
wrote:

> It is hung on "Waiting for jenkinks.impala.io" for a while and
> eventually responds with a HTTP 504. Tried it on two different machines and
> two different browsers.
>
> Anyone else facing this issue?
>

Update JIRA Issues with Commit Message

[Fredy Wijaya]

Hi all,

ASF JIRA Bot was down, it's up now (
https://issues.apache.org/jira/browse/INFRA-17134) and if your JIRA issues
are in the list below, can you copy and paste the git commit message into
these JIRA issues for tracking purposes. Thanks.

* 0047191 IMPALA-7693: stress test: fix Query().name (25 hours ago)

* 0cbe37a IMPALA-7688: Fix spurious error messages when updating owner
privileges (33 hours ago) 
* 6099255 IMPALA-7682: Make AuthorizationPolicy thread-safe (2 days ago)

* e8ee827 [DOCS] Built-in Functions doc format Changes (2 days ago) 
* b0d0d73 IMPALA-7680: [DOCS] Minor edits to the command line config
section (2 days ago) 
* 8ca7926 [DOCS] Copy edited the Cancelling a Query section (2 days ago)

* 53decbc IMPALA-7676: DESCRIBE on table should require VIEW_METADATA
privilege (2 days ago) 
* 9ac874d IMPALA-7684: Fix Admission result printed in the query profile (3
days ago) 
* 6568e6e IMPALA-7607: [DOCS] Add a reference to EXEC_TIME_LIMIT_S to
TIMEOUT doc (3 days ago) 
* 7b13117 IMPALA-7654: [DOCS] TRUNCATE does not put HDFS data files to the
trash (3 days ago) 
* ee3da43 Prettify the timeline produced by test-with-docker.py (3 days
ago) 
* 122c366 IMPALA-7675: Fix the error handling of UpdateTableUsage() RPC (3
days ago) 
* d05f73f IMPALA-7647: Add HS2/Impyla dimension to TestQueries (4 days ago)

* fec2d64 IMPALA-7678: Revert "IMPALA-7660: Support ECDH ciphers for debug
webserver" (4 days ago) 
* 51cc1d2 IMPALA-7623: [DOCS] Disallow name changes for managed Kudu tables
(4 days ago) 
* d48ffc2 IMPALA-7626: Throttle catalog partial RPC requests (4 days ago)

* 843683e IMPALA-7644: Hide Parquet page index writing with feature flag (4
days ago) 
* e5c502e IMPALA-7671: Fix broken SHOW GRANT USER ON  (6 days ago)

* 81c58d5 IMPALA-7643: report # queries actually executing in stress test
(7 days ago) 
* d3db326 IMPALA-2063 Remove newline characters in query status. (7 days
ago) 
* f8b2eb5 IMPALA-7661: Increase the sleep time in test_reconnect (7 days
ago) 
* 0e1de31 IMPALA-7660: Support ECDH ciphers for debug webserver (7 days
ago) 
* 37bee3a IMPALA-7633: count_user_privilege isn't 0 at the end of
test_owner (7 days ago) 
* 23428dc IMPALA-7651: [DOCS] Kudu support to scheduler-related query hints
and options (7 days ago) 
* 1914a8b IMPALA-7667: sentry.db.explicit.grants.permitted does not accept
empty value (7 days ago) 
* 3a37c72 IMPALA-7484: Do not interpret unrecognized hints as straight_join
hints. (7 days ago) 

Re: Build failed in 2.x and 2.12.0-release due to updates of sentry-1.5.1-cdh5.16.0-SNAPSHOT

[Fredy Wijaya]

Hi Quanglong,

I'm working on a fix: https://issues.apache.org/jira/browse/IMPALA-7513. CR
is here: https://gerrit.cloudera.org/c/11362/
I agree that the dependencies should be frozen. Feel free to file a JIRA
for the 2.x branch to use the released versions instead of the SNAPSHOT
versions to make the build more stable.

On Thu, Aug 30, 2018 at 4:38 AM Quanlong Huang 
wrote:

> Hi all,
>
> Recently, Sentry in version 1.5.1-cdh5.16.0-SNAPSHOT is updated, which
> breaks the build of 2.x branch and even 2.12.0-release. The error is
>
> [ERROR]
>
> /tmp/jenkins/workspace/impala-compile-and-publish/fe/src/main/java/org/apache/impala/catalog/AuthorizationPolicy.java:[58,8]
> org.apache.impala.catalog.AuthorizationPolicy is not abstract and does not
> override abstract method
>
> listPrivileges(java.util.Set,java.util.Set,org.apache.sentry.core.common.ActiveRoleSet)
> in org.apache.sentry.provider.cache.PrivilegeCache
>
> My question is why we depend on CDH SNAPSHOT versions even in a release? I
> think the dependencies of a release should be frozen. However, there're no
> stable version of cdh dependencies downloadable in
> https://native-toolchain.s3.amazonaws.com. Could you help to upload stable
> version of these cdh dependencies?
>
> Thanks,
> Quanlong
>

Re: New Impala committer - Quanlong Huang

[Fredy Wijaya]

Congrats!

On Fri, Aug 17, 2018 at 2:09 PM Yongjun Zhang  wrote:

> Congratulations Quanlong!
>
> --Yngjun
>
> On Fri, Aug 17, 2018 at 12:07 PM, Jeszy  wrote:
>
> > Congrats Quanlong!
> >
> > On 17 August 2018 at 19:51, Csaba Ringhofer 
> > wrote:
> > > Congrats!
> > >
> > > On Fri, Aug 17, 2018 at 6:32 PM, Philip Zeyliger 
> > > wrote:
> > >
> > >> Congrats!
> > >>
> > >> On Fri, Aug 17, 2018 at 9:29 AM Tim Armstrong <
> tarmstr...@cloudera.com>
> > >> wrote:
> > >>
> > >> >  The Project Management Committee (PMC) for Apache Impala has
> invited
> > >> > Quanlong Huang to become a committer and we are pleased to announce
> > that
> > >> > they have accepted. Congratulations and welcome, Quanlong Huang!
> > >> >
> > >>
> >
>

Re: Help with task: Warn if deprecated flags are set

[Fredy Wijaya]

Hi,

Unfortunately that ticket has already been resolved:
https://issues.apache.org/jira/browse/IMPALA-5610
We have other tickets labelled as newbie if you're interested:
https://issues.apache.org/jira/browse/IMPALA-6844?jql=project%20%3D%20IMPALA%20AND%20labels%20%3D%20newbie%20AND%20assignee%20in%20(EMPTY)

On Sun, Jul 29, 2018 at 7:10 PM trinhvan hop 
wrote:

> I would like to help out with the task listed at
> https://helpwanted.apache.org/task.html?bdba0fee
>
>
>
> Được gửi từ Windows Phone của tôi
>

Re: Broken Impala Build?

[Fredy Wijaya]

The CR is merged and the build looks good now. Please remove
$IMPALA_HOME/toolchain and run a full build (./buildall.sh -format
-testdata -notests). It's also recommended to exit any shell sessions to
avoid issue related to stale environment variable.

On Wed, Jul 18, 2018 at 2:16 PM Fredy Wijaya  wrote:

> ​A CR to fix the issue: https://gerrit.cloudera.org/c/10981/
> I'm running a dry-run to make sure everything is good with the new build
> number.​
>
> On Wed, Jul 18, 2018 at 12:24 PM Todd Lipcon 
> wrote:
>
>> Yea, I just got the same on a gerrit build. I would guess this somehow
>> means we are ending up with mismatched versions of the "HDFS" and "common"
>> Hadoop jars on our classpath. Possibly one is getting picked up from Maven
>> whereas another is getting picked up from toolchain?
>>
>> -Todd
>>
>> On Wed, Jul 18, 2018 at 10:21 AM, Fredy Wijaya
>> > > wrote:
>>
>> > I got this error trying to do a clean build in HEAD. Did anyone
>> encounter
>> > the same issue?
>> >
>> > I0718 10:03:13.658380 23734 jni-util.cc:230]
>> > java.lang.NoClassDefFoundError:
>> > org/apache/hadoop/fs/Options$ChecksumCombineMode
>> > at
>> > org.apache.hadoop.hdfs.client.impl.DfsClientConf.
>> > getChecksumCombineModeFromConf(DfsClientConf.java:314)
>> > at
>> > org.apache.hadoop.hdfs.client.impl.DfsClientConf.(
>> > DfsClientConf.java:184)
>> > at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:302)
>> > at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:286)
>> > at
>> > org.apache.hadoop.hdfs.DistributedFileSystem.initialize(
>> > DistributedFileSystem.java:167)
>> > at
>> > org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:3288)
>> > at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:123)
>> > at
>> > org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:3337)
>> > at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:3305)
>> > at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:476)
>> > at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:225)
>> > at
>> > org.apache.impala.service.JniFrontend.checkFileSystem(
>> > JniFrontend.java:778)
>> > at
>> > org.apache.impala.service.JniFrontend.checkConfiguration(
>> > JniFrontend.java:690)
>> > I0718 10:03:13.659090 23734 status.cc:125] NoClassDefFoundError:
>> > org/apache/hadoop/fs/Options$ChecksumCombineMode
>> > @  0x1951b3a
>> > @  0x1ff307f
>> > @  0x1e9ec51
>> > @  0x1eba8bb
>> > @  0x1eb6df2
>> > @  0x190d4bf
>> > @ 0x7fe6e95bf82f
>> > @  0x190d338
>> > E0718 10:03:13.659101 23734 impala-server.cc:289] NoClassDefFoundError:
>> > org/apache/hadoop/fs/Options$ChecksumCombineMode
>> > E0718 10:03:13.659122 23734 impala-server.cc:292] Aborting Impala Server
>> > startup due to improper configuration. Impalad exiting.
>> >
>>
>>
>>
>> --
>> Todd Lipcon
>> Software Engineer, Cloudera
>>
>

Re: Broken Impala Build?

[Fredy Wijaya]

​A CR to fix the issue: https://gerrit.cloudera.org/c/10981/
I'm running a dry-run to make sure everything is good with the new build
number.​

On Wed, Jul 18, 2018 at 12:24 PM Todd Lipcon 
wrote:

> Yea, I just got the same on a gerrit build. I would guess this somehow
> means we are ending up with mismatched versions of the "HDFS" and "common"
> Hadoop jars on our classpath. Possibly one is getting picked up from Maven
> whereas another is getting picked up from toolchain?
>
> -Todd
>
> On Wed, Jul 18, 2018 at 10:21 AM, Fredy Wijaya
>  > wrote:
>
> > I got this error trying to do a clean build in HEAD. Did anyone encounter
> > the same issue?
> >
> > I0718 10:03:13.658380 23734 jni-util.cc:230]
> > java.lang.NoClassDefFoundError:
> > org/apache/hadoop/fs/Options$ChecksumCombineMode
> > at
> > org.apache.hadoop.hdfs.client.impl.DfsClientConf.
> > getChecksumCombineModeFromConf(DfsClientConf.java:314)
> > at
> > org.apache.hadoop.hdfs.client.impl.DfsClientConf.(
> > DfsClientConf.java:184)
> > at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:302)
> > at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:286)
> > at
> > org.apache.hadoop.hdfs.DistributedFileSystem.initialize(
> > DistributedFileSystem.java:167)
> > at
> > org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:3288)
> > at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:123)
> > at
> > org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:3337)
> > at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:3305)
> > at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:476)
> > at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:225)
> > at
> > org.apache.impala.service.JniFrontend.checkFileSystem(
> > JniFrontend.java:778)
> > at
> > org.apache.impala.service.JniFrontend.checkConfiguration(
> > JniFrontend.java:690)
> > I0718 10:03:13.659090 23734 status.cc:125] NoClassDefFoundError:
> > org/apache/hadoop/fs/Options$ChecksumCombineMode
> > @  0x1951b3a
> > @  0x1ff307f
> > @  0x1e9ec51
> > @  0x1eba8bb
> > @  0x1eb6df2
> > @  0x190d4bf
> > @ 0x7fe6e95bf82f
> > @  0x190d338
> > E0718 10:03:13.659101 23734 impala-server.cc:289] NoClassDefFoundError:
> > org/apache/hadoop/fs/Options$ChecksumCombineMode
> > E0718 10:03:13.659122 23734 impala-server.cc:292] Aborting Impala Server
> > startup due to improper configuration. Impalad exiting.
> >
>
>
>
> --
> Todd Lipcon
> Software Engineer, Cloudera
>

Broken Impala Build?

[Fredy Wijaya]

I got this error trying to do a clean build in HEAD. Did anyone encounter
the same issue?

I0718 10:03:13.658380 23734 jni-util.cc:230]
java.lang.NoClassDefFoundError:
org/apache/hadoop/fs/Options$ChecksumCombineMode
at
org.apache.hadoop.hdfs.client.impl.DfsClientConf.getChecksumCombineModeFromConf(DfsClientConf.java:314)
at
org.apache.hadoop.hdfs.client.impl.DfsClientConf.(DfsClientConf.java:184)
at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:302)
at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:286)
at
org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.java:167)
at
org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:3288)
at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:123)
at
org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:3337)
at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:3305)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:476)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:225)
at
org.apache.impala.service.JniFrontend.checkFileSystem(JniFrontend.java:778)
at
org.apache.impala.service.JniFrontend.checkConfiguration(JniFrontend.java:690)
I0718 10:03:13.659090 23734 status.cc:125] NoClassDefFoundError:
org/apache/hadoop/fs/Options$ChecksumCombineMode
@  0x1951b3a
@  0x1ff307f
@  0x1e9ec51
@  0x1eba8bb
@  0x1eb6df2
@  0x190d4bf
@ 0x7fe6e95bf82f
@  0x190d338
E0718 10:03:13.659101 23734 impala-server.cc:289] NoClassDefFoundError:
org/apache/hadoop/fs/Options$ChecksumCombineMode
E0718 10:03:13.659122 23734 impala-server.cc:292] Aborting Impala Server
startup due to improper configuration. Impalad exiting.

Re: Re: Removing IMPALA_MINICLUSTER_PROFILE=2 from master

[Fredy Wijaya]

The work to remove IMPALA_MINICLUSTER_PROFILE=2 from master is complete.
Please run a full build (./buildall.sh -notests -format -testdata) to avoid
any issues. Though not strictly necessary, it's recommended to exit the
shell session to avoid potential issues related to stale environment
variables. Sorry for the inconvenience.

On Wed, Jul 11, 2018 at 8:51 PM Jim Apple 
wrote:

> The tricky thing about backporting all bug-fixes is that 41 of the 91
> resolved issues in the past four weeks are bugs:
>
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20IMPALA%20AND%20issuetype%20%3D%20Bug%20AND%20resolution%20%3D%20Fixed%20AND%20resolved%20%3E%3D%20-4w%20ORDER%20BY%20issuetype%20DESC%2C%20created%20DESC
>
> Backporting all of them could be substantial labor requiring the dedicated
> attention of a committer.
>
> That said, not all of those JIRAs are correctly typed (some may be
> improvements), and it might be possible to backport a most critical subset
> to 2.x without heavy commitment from a committer as long as someone,
> committer or not takes the lead.
>
>
> On Wed, Jul 11, 2018 at 5:55 PM, Quanlong Huang 
> wrote:
>
> > So there're no more official supports for Hadoop 2, even for bug-fix? I
> > know the master branch may have only support Hadoop 3 with full test
> > coverage now. But I don't identify with you to abandon users in Hadoop 2.
> > What if they encounter a critical bug in impala-2.12 and can not upgrade
> > their heavy cluster to Hadoop3?
> >
> >
> > I'm +1 for this if we can bring 2.x branch back to live even we only
> patch
> > bug-fixes on it.
> >
> > At 2018-07-12 02:31:44, "Bikramjeet Vig"  .INVALID>
> > wrote:
> > >+1 on removing it.
> > >
> > >On Wed, Jul 11, 2018 at 10:49 AM, Philip Zeyliger <
> > >phi...@cloudera.com.invalid> wrote:
> > >
> > >> I'm +1 on removing it.
> > >>
> > >> On Wed, Jul 11, 2018 at 9:39 AM Sailesh Mukil
> >  > >> >
> > >> wrote:
> > >>
> > >> > +1 for removing it.
> > >> >
> > >> > I'm all for reduced complexity if not a lot of users are benefitting
> > from
> > >> > it.
> > >> >
> > >> > On Wed, Jul 11, 2018 at 9:29 AM, Fredy Wijaya
> > >>  > >> > >
> > >> > wrote:
> > >> >
> > >> > > Hi all,
> > >> > >
> > >> > > In the master branch, we support both Hadoop 2 and Hadoop 3 via
> > >> > > IMPALA_MINICLUSTER_PROFILE environment variable. When Impala
> > >> transitioned
> > >> > > from Hadoop 2 to Hadoop 3, we introduced
> IMPALA_MINICLUSTER_PROFILE
> > as
> > >> a
> > >> > > way to easily switch between Hadoop 2 and Hadoop 3. It made sense
> at
> > >> that
> > >> > > time. However, I believe the IMPALA_MINICLUSTER_PROFILE=2 has
> > outlived
> > >> > its
> > >> > > usefulness and has grown more complex to maintain given that we
> > need to
> > >> > > introduce shims, feature flags, additional Jenkins jobs, etc.
> Given
> > >> that
> > >> > we
> > >> > > already have 2.x branch for Impala with Hadoop 2 support. I'm
> > proposing
> > >> > > that we remove IMPALA_MINICLUSTER_PROFILE=2 in the master branch
> so
> > >> that
> > >> > we
> > >> > > can focus our effort on supporting Hadoop 3 on the master branch.
> > >> > >
> > >> > > What do others think?
> > >> > >
> > >> >
> > >>
> >
>

Re: Re: Build failure due to access denied to S3 resources

[Fredy Wijaya]

] |  +- org.apache.htrace:htrace-core4:jar:4.1.0-incubating:compile
[INFO] |  +-
org.apache.zookeeper:zookeeper:jar:3.4.5-cdh6.x-SNAPSHOT:compile
[INFO] |  |  +- jline:jline:jar:2.12:compile
[INFO] |  |  +- io.netty:netty:jar:3.10.5.Final:compile
[INFO] |  |  \- org.apache.yetus:audience-annotations:jar:0.5.0:compile
[INFO] |  +- org.apache.commons:commons-compress:jar:1.4.1:compile
[INFO] |  +- org.apache.kerby:kerb-simplekdc:jar:1.0.0:compile
[INFO] |  |  +- org.apache.kerby:kerb-client:jar:1.0.0:compile
[INFO] |  |  |  +- org.apache.kerby:kerby-config:jar:1.0.0:compile
[INFO] |  |  |  +- org.apache.kerby:kerb-core:jar:1.0.0:compile
[INFO] |  |  |  |  \- org.apache.kerby:kerby-pkix:jar:1.0.0:compile
[INFO] |  |  |  | +- org.apache.kerby:kerby-asn1:jar:1.0.0:compile
[INFO] |  |  |  | \- org.apache.kerby:kerby-util:jar:1.0.0:compile
[INFO] |  |  |  +- org.apache.kerby:kerb-common:jar:1.0.0:compile
[INFO] |  |  |  |  \- org.apache.kerby:kerb-crypto:jar:1.0.0:compile
[INFO] |  |  |  \- org.apache.kerby:kerb-util:jar:1.0.0:compile
[INFO] |  |  \- org.apache.kerby:kerb-admin:jar:1.0.0:compile
[INFO] |  | +- org.apache.kerby:kerb-server:jar:1.0.0:compile
[INFO] |  | |  \- org.apache.kerby:kerb-identity:jar:1.0.0:compile
[INFO] |  | \- org.apache.kerby:kerby-xdr:jar:1.0.0:compile
[INFO] |  +- com.fasterxml.jackson.core:jackson-databind:jar:2.9.5:compile
[INFO] |  +- org.codehaus.woodstox:stax2-api:jar:3.1.4:compile
[INFO] |  \- com.fasterxml.woodstox:woodstox-core:jar:5.0.3:compile
[INFO] +-
org.apache.hadoop:hadoop-yarn-api:jar:3.0.0-cdh6.x-SNAPSHOT:compile
[INFO] |  +- javax.xml.bind:jaxb-api:jar:2.2.11:compile
[INFO] |  \-
com.fasterxml.jackson.core:jackson-annotations:jar:2.9.5:compile
[INFO] \-
org.apache.hadoop:hadoop-yarn-common:jar:3.0.0-cdh6.x-SNAPSHOT:compile
[INFO]+-
org.apache.hadoop:hadoop-hdfs-client:jar:3.0.0-cdh6.x-SNAPSHOT:compile
[INFO]|  \- com.squareup.okhttp:okhttp:jar:2.7.5:compile
[INFO]| \- com.squareup.okio:okio:jar:1.6.0:compile
[INFO]+- com.sun.jersey:jersey-client:jar:1.19:compile
[INFO]+- com.google.inject.extensions:guice-servlet:jar:4.0:compile
[INFO]+- com.google.inject:guice:jar:4.0:compile
[INFO]|  +- javax.inject:javax.inject:jar:1:compile
[INFO]|  \- aopalliance:aopalliance:jar:1.0:compile
[INFO]+- com.sun.jersey.contribs:jersey-guice:jar:1.19:compile
[INFO]+- com.fasterxml.jackson.core:jackson-core:jar:2.9.5:compile
[INFO]+-
com.fasterxml.jackson.module:jackson-module-jaxb-annotations:jar:2.9.5:compile
[INFO]\-
com.fasterxml.jackson.jaxrs:jackson-jaxrs-json-provider:jar:2.9.5:compile
[INFO]   \-
com.fasterxml.jackson.jaxrs:jackson-jaxrs-base:jar:2.9.5:compile

​​
On Wed, Jul 4, 2018, 7:40 AM Quanlong Huang  wrote:

> Hi Fredy,
>
>
> Thanks for looking into this. But try deleting $HOME/.m2 and
> $IMPALA_HOME/toolchain does not help.
>
>
> $HOME/.m2 is the local repository of maven which acts as a cache for pom
> files and jars. I think you have built successfully when you have access to
> Cloudera network. Once the files are cached in $HOME/.m2, your build can
> still succeed unless the dependencies' versions change.
>
>
> Could you try to remove (or just move away)
> $HOME/.m2/repository/org/codehaus/jackson/jackson-mapper-asl/1.9.13-cloudera.1
> and see if you can build FE without access to Cloudera network?
> Can you access the following link outside of Cloudera network?
> https://native-toolchain.s3.amazonaws.com/build/cdh_components/422770/maven/org/codehaus/jackson/jackson-mapper-asl/1.9.13-cloudera.1/
> ​​
> jackson-mapper-asl-1.9.13-cloudera.1.pom
> <https://native-toolchain.s3.amazonaws.com/build/cdh_components/422770/maven/org/codehaus/jackson/jackson-mapper-asl/1.9.13-cloudera.1/jackson-mapper-asl-1.9.13-cloudera.1.pom>
>
>
> Thanks,
> Quanlong
>
> At 2018-07-04 14:40:47, "Fredy Wijaya" 
> wrote:
> >Hi Quanlong,
> >
> >I'm able to build Impala on my personal computer without any access to
> >Cloudera network. Can you try to delete $HOME/.m2 and
> >$IMPALA_HOME/toolchain and run the build again?
> >
> >On Tue, Jul 3, 2018 at 11:45 PM Quanlong Huang 
> >wrote:
> >
> >> Hi Cloudera folks,
> >>
> >>
> >> Recently, I'm building the master branch in my dev machine. It failed at
> >> building yarn-extras with the following logs:
> >>
> >>
> >>
> >> [INFO] BUILD FAILURE
> >>
> >> [ERROR] Failed to execute goal on project yarn-extras: Could not resolve
> >> dependencies for project org.apache.impala:yarn-extras:jar:0.1-SNAPSHOT:
> >> Failed to collect dependencies for [net.minidev:json-smart:jar
> >>
> >> :2.3 (compile),
> org.apache.hadoop:hadoop-common:jar:3.0.0-cdh6.x-SNAPSHOT
> >> (compile), 

Re: Java 7 support

[Fredy Wijaya]

I was wondering about that myself especially since we already use Java 8
compiler but with source and target set to 1.7: https://github.com/
apache/impala/blob/master/fe/pom.xml#L289-L290

On Wed, May 30, 2018 at 4:17 PM, Bharath Vissapragada  wrote:

> Does Impala still support Java 7? There are lot of interesting Java 8
> constructs that we could use in the code, but wondering if that breaks any
> compatibility. Thoughts?
>
> There is not much information in the docs btw.
>
> 3.x
> https://impala.apache.org/docs/build3x/html/topics/impala_
> prereqs.html#prereqs
> 2.x
> https://impala.apache.org/docs/build/html/topics/impala_prer
> eqs.html#prereqs
>

Re: Build error with sqlparse-0.1.14

[Fredy Wijaya]

We could also set the PYTHONPATH to be more explicit instead of using a
wildcard:
https://github.com/apache/impala/blob/master/bin/set-pythonpath.sh#L39

Thoughts?

*Fredy Wijaya* | Software Engineer
e. fwij...@cloudera.com
cloudera.com <https://www.cloudera.com>

[image: Cloudera] <https://www.cloudera.com/>

[image: Cloudera on Twitter] <https://twitter.com/cloudera> [image:
Cloudera on Facebook] <https://www.facebook.com/cloudera> [image: Cloudera
on LinkedIn] <https://www.linkedin.com/company/cloudera>
--

On Fri, May 11, 2018 at 11:31 AM, Fredy Wijaya <fwij...@cloudera.com> wrote:

> Thanks Tim. I was about to email the same thing.
>
> On Fri, May 11, 2018 at 11:28 AM, Tim Armstrong <tarmstr...@cloudera.com>
> wrote:
>
>> Just an FYI, since everyone else is probably going to run into this. The
>> sqlparse version change breaks buildall.sh if you run it on a non-clean
>> tree.
>>
>> Creating an egg for
>> /home/tarmstrong/Impala/incubator-impala/shell/ext-py/sqlparse-0.1.14
>> python: can't open file 'setup.py': [Errno 2] No such file or directory
>> Error in
>> /home/tarmstrong/Impala/incubator-impala/shell/make_shell_tarball.sh at
>> line 96: python setup.py -q bdist_egg clean
>>
>> The fix is to delete any leftover files from the old sqlparse version:
>>
>> $  rm -rf shell/ext-py/sqlparse-0.1.14/
>>
>
>

Re: Build error with sqlparse-0.1.14

[Fredy Wijaya]

Thanks Tim. I was about to email the same thing.

On Fri, May 11, 2018 at 11:28 AM, Tim Armstrong 
wrote:

> Just an FYI, since everyone else is probably going to run into this. The
> sqlparse version change breaks buildall.sh if you run it on a non-clean
> tree.
>
> Creating an egg for
> /home/tarmstrong/Impala/incubator-impala/shell/ext-py/sqlparse-0.1.14
> python: can't open file 'setup.py': [Errno 2] No such file or directory
> Error in
> /home/tarmstrong/Impala/incubator-impala/shell/make_shell_tarball.sh at
> line 96: python setup.py -q bdist_egg clean
>
> The fix is to delete any leftover files from the old sqlparse version:
>
> $  rm -rf shell/ext-py/sqlparse-0.1.14/
>

Re: Bulk Cherry-Pick FGP Commits to 2.x Branch

[Fredy Wijaya]

Yeah "Fine-grained Privileges".


On Wed, Apr 25, 2018 at 3:13 PM, Bharath Vissapragada <bhara...@cloudera.com
> wrote:

> FGP = "Fine-grained privileges" or something else?
>
> On Wed, Apr 25, 2018 at 1:09 PM, Fredy Wijaya <fwij...@cloudera.com>
> wrote:
>
> > Hi,
> >
> > Just to give a heads-up, I'll do bulk cherry-pick FGP commits to 2.x
> > branch. Build is passing in the private build and Alex has verified it.
> >
> > Let me know if you have any concerns.
> >
> > Thanks,
> > Fredy
> >
>

Bulk Cherry-Pick FGP Commits to 2.x Branch

[Fredy Wijaya]

Hi,

Just to give a heads-up, I'll do bulk cherry-pick FGP commits to 2.x
branch. Build is passing in the private build and Alex has verified it.

Let me know if you have any concerns.

Thanks,
Fredy

Re: Impala FE compilation error (related to sentry)

[Fredy Wijaya]

In Sentry 1.5.1, BitFieldAction is an abstract class:
https://github.com/apache/sentry/blob/release-1.5.1/sentry-core/sentry-core-common/src/main/java/org/apache/sentry/core/common/BitFieldAction.java#L22.
Sentry removed the abstract requirement in Sentry 2.0.0:
https://github.com/apache/sentry/blob/master/sentry-core/sentry-core-common/src/main/java/org/apache/sentry/core/common/BitFieldAction.java#L23

To support both versions of Sentry, we need to fix
https://github.com/apache/impala/blob/master/fe/src/main/java/org/apache/impala/authorization/Privilege.java#L72
.

*Fredy Wijaya* | Software Engineer
e. fwij...@cloudera.com
cloudera.com <https://www.cloudera.com>

[image: Cloudera] <https://www.cloudera.com/>

[image: Cloudera on Twitter] <https://twitter.com/cloudera> [image:
Cloudera on Facebook] <https://www.facebook.com/cloudera> [image: Cloudera
on LinkedIn] <https://www.linkedin.com/company/cloudera>
--

On Mon, Apr 16, 2018 at 5:10 PM, Sailesh Mukil <sail...@cloudera.com> wrote:

> I get this error when trying to the build the Impala frontend. Anyone know
> how I can get past this?
>
> [ERROR] COMPILATION ERROR :
>
> [ERROR]
> /home/systest/incubator-impala/fe/src/main/java/org/
> apache/impala/authorization/Privilege.java:[72,25]
> org.apache.sentry.core.common.BitFieldAction is abstract; cannot be
> instantiated
>
> [INFO] BUILD FAILURE
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.3:compile
> (default-compile) on project impala-frontend: Compilation failure
>
> [ERROR]
> /home/systest/incubator-impala/fe/src/main/java/org/
> apache/impala/authorization/Privilege.java:[72,25]
> org.apache.sentry.core.common.BitFieldAction is abstract; cannot be
> instantiated
>
> [ERROR] -> [Help 1]
>
> [ERROR]
>
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
>
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>
> [ERROR]
>
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
>
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>

CWiki Write Access

[Fredy Wijaya]

Hello,

Can I request for a write access for CWiki?

Thanks,
Fredy

Please Add Me as an Impala Contributor

[Fredy Wijaya]

My JIRA username is fredyw.

*Fredy Wijaya* | Software Engineer
e. fwij...@cloudera.com
cloudera.com <https://www.cloudera.com>

[image: Cloudera] <https://www.cloudera.com/>

[image: Cloudera on Twitter] <https://twitter.com/cloudera> [image:
Cloudera on Facebook] <https://www.facebook.com/cloudera> [image: Cloudera
on LinkedIn] <https://www.linkedin.com/company/cloudera>
--