[
https://issues.apache.org/jira/browse/SENTRY-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16339478#comment-16339478
]
Na Li commented on SENTRY-2127:
---
The actual problem is MapRedTask sometimes fail with more complicated join
[
https://issues.apache.org/jira/browse/SENTRY-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-2127:
--
Attachment: SENTRY-2127.001.patch
> Fix unstable unit test TestColumnEndToEnd.testCrossDbTableOperations
>
[
https://issues.apache.org/jira/browse/SENTRY-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-2127:
--
Status: Patch Available (was: Open)
> Fix unstable unit test TestColumnEndToEnd.testCrossDbTableOperations
>
[
https://issues.apache.org/jira/browse/SENTRY-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-2127:
--
Description:
Occasionally, the test TestColumnEndToEnd.testCrossDbTableOperations fails at
statement
Na Li created SENTRY-2127:
-
Summary: Fix unstable unit test
TestColumnEndToEnd.testCrossDbTableOperations
Key: SENTRY-2127
URL: https://issues.apache.org/jira/browse/SENTRY-2127
Project: Sentry
[
https://issues.apache.org/jira/browse/SENTRY-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-2091:
--
Attachment: SENTRY-2091.006.patch
> User-based Privilege is broken by SENTRY-769
>
[
https://issues.apache.org/jira/browse/SENTRY-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li reassigned SENTRY-1648:
-
Assignee: Na Li
> Sentry MySQL "Unique" Index
> ---
>
> Key:
[
https://issues.apache.org/jira/browse/SENTRY-2123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-2123:
--
Description:
Thrift source code is generated and put in its separate directory. Without
providing its path to
[
https://issues.apache.org/jira/browse/SENTRY-2123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-2123:
--
Summary: Specify code path of auth-generated thrift files for Javadoc and
exclude them from Javadoc generation
[
https://issues.apache.org/jira/browse/SENTRY-2123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-2123:
--
Attachment: SENTRY-2123.002.patch
> Specify Thrift source code path for Javadoc
>
[
https://issues.apache.org/jira/browse/SENTRY-2118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li closed SENTRY-2118.
-
> Document Configuration required to make Column authentication work
>
[
https://issues.apache.org/jira/browse/SENTRY-2118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-2118:
--
Fix Version/s: 2.1.0
> Document Configuration required to make Column authentication work
>
[
https://issues.apache.org/jira/browse/SENTRY-2123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330886#comment-16330886
]
Na Li commented on SENTRY-2123:
---
Since HDFS-common and provider-db project import generated sentry thrift
[
https://issues.apache.org/jira/browse/SENTRY-2123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-2123:
--
Attachment: SENTRY-2123.001.patch
> Specify Thrift source code path for Javadoc
>
Na Li created SENTRY-2123:
-
Summary: Specify Thrift source code path for Javadoc
Key: SENTRY-2123
URL: https://issues.apache.org/jira/browse/SENTRY-2123
Project: Sentry
Issue Type: Bug
[
https://issues.apache.org/jira/browse/SENTRY-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-2120:
--
Summary: Escape input string for error response message in LogLevelServlet
(was: Potential cross-site
[
https://issues.apache.org/jira/browse/SENTRY-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-2120:
--
Description:
LogLevelServlet.java has the following code
{code}
public void doGet(HttpServletRequest
[
https://issues.apache.org/jira/browse/SENTRY-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322583#comment-16322583
]
Na Li commented on SENTRY-2119:
---
[~kkalyan] Is it possible for event_id to have permanent gap? If so, then
[
https://issues.apache.org/jira/browse/SENTRY-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322560#comment-16322560
]
Na Li commented on SENTRY-2121:
---
"Another option is to always trigger a full snapshot every time HDFS sync
[
https://issues.apache.org/jira/browse/SENTRY-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16321458#comment-16321458
]
Na Li commented on SENTRY-2121:
---
To solve this issue, we have two options:
1) When HDFS is disabled, we
[
https://issues.apache.org/jira/browse/SENTRY-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-2120:
--
Summary: Potential cross-site scripting in LogLevelServlet (was:
cross-site scripting vulnerability in
[
https://issues.apache.org/jira/browse/SENTRY-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-2120:
--
Description:
LogLevelServlet.java has the following code
{code}
public void doGet(HttpServletRequest
[
https://issues.apache.org/jira/browse/SENTRY-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-2120:
--
Attachment: SENTRY-2120.001.patch
v1. attach again to trigger the test. the failed test is timeout, and it
[
https://issues.apache.org/jira/browse/SENTRY-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-2120:
--
Labels: Fortify-Critical (was: )
> cross-site scripting vulnerability in LogLevelServlet
>
[
https://issues.apache.org/jira/browse/SENTRY-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-2120:
--
Attachment: SENTRY-2120.001.patch
> cross-site scripting vulnerability in LogLevelServlet
>
[
https://issues.apache.org/jira/browse/SENTRY-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-2120:
--
Status: Patch Available (was: Open)
> cross-site scripting vulnerability in LogLevelServlet
>
Na Li created SENTRY-2120:
-
Summary: cross-site scripting vulnerability in LogLevelServlet
Key: SENTRY-2120
URL: https://issues.apache.org/jira/browse/SENTRY-2120
Project: Sentry
Issue Type: Bug
[
https://issues.apache.org/jira/browse/SENTRY-2118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li resolved SENTRY-2118.
---
Resolution: Fixed
The description is at
[
https://issues.apache.org/jira/browse/SENTRY-2118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16313493#comment-16313493
]
Na Li commented on SENTRY-2118:
---
[~coheig] has found this issue, and it is fixed by adding this
Na Li created SENTRY-2118:
-
Summary: Document Configuration required to make Column
authentication work
Key: SENTRY-2118
URL: https://issues.apache.org/jira/browse/SENTRY-2118
Project: Sentry
Issue
[
https://issues.apache.org/jira/browse/SENTRY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16311884#comment-16311884
]
Na Li commented on SENTRY-2109:
---
[~kkalyan] the purging uses ID - 100. It does not guarantee that we have
[
https://issues.apache.org/jira/browse/SENTRY-2114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16311633#comment-16311633
]
Na Li commented on SENTRY-2114:
---
We should process notifications just to update the ID and wake up the
[
https://issues.apache.org/jira/browse/SENTRY-2114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16310252#comment-16310252
]
Na Li commented on SENTRY-2114:
---
How to handle the following case correctly?
1. HDFS is disabled
2. HDFS is
[
https://issues.apache.org/jira/browse/SENTRY-2114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16310249#comment-16310249
]
Na Li commented on SENTRY-2114:
---
The default value of sentry last notification ID should be 0. So the step
[
https://issues.apache.org/jira/browse/SENTRY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16308834#comment-16308834
]
Na Li commented on SENTRY-2109:
---
[~kkalyan] Sentry service periodically calls purgeNotificationIdTable.
[
https://issues.apache.org/jira/browse/SENTRY-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-2091:
--
Attachment: SENTRY-2091.004.patch
v4 again to trigger the test
> User-based Privilege is broken by SENTRY-769
[
https://issues.apache.org/jira/browse/SENTRY-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-2091:
--
Attachment: SENTRY-2091.004.patch
v4. fix more hive test failure
> User-based Privilege is broken by
[
https://issues.apache.org/jira/browse/SENTRY-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291392#comment-16291392
]
Na Li commented on SENTRY-2096:
---
[~kkalyan] [~spena] Based on my testing results, we should use
[
https://issues.apache.org/jira/browse/SENTRY-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16289715#comment-16289715
]
Na Li commented on SENTRY-1753:
---
and the solution is very simple.
> Make HMSFollower initial delay
Na Li created SENTRY-2100:
-
Summary: Create user related ACL at Name Node
Key: SENTRY-2100
URL: https://issues.apache.org/jira/browse/SENTRY-2100
Project: Sentry
Issue Type: Sub-task
Na Li created SENTRY-2099:
-
Summary: Add user to role mapping in thrift response for
permission updates
Key: SENTRY-2099
URL: https://issues.apache.org/jira/browse/SENTRY-2099
Project: Sentry
Issue
[
https://issues.apache.org/jira/browse/SENTRY-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16289606#comment-16289606
]
Na Li edited comment on SENTRY-1753 at 12/13/17 5:42 PM:
-
[~liamsargent] the
[
https://issues.apache.org/jira/browse/SENTRY-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16289606#comment-16289606
]
Na Li commented on SENTRY-1753:
---
[~liamsargent] the default value right now is 0
[
https://issues.apache.org/jira/browse/SENTRY-2097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16288467#comment-16288467
]
Na Li commented on SENTRY-2097:
---
We should document this, so user won't revoke privileges in this way
To
[
https://issues.apache.org/jira/browse/SENTRY-2097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li reassigned SENTRY-2097:
-
Assignee: Na Li
> Sentry privileges model: Can Sentry take a database privileges away from a
> server
[
https://issues.apache.org/jira/browse/SENTRY-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-2096:
--
Status: Patch Available (was: Open)
> Fail unit tests at end
> --
>
>
[
https://issues.apache.org/jira/browse/SENTRY-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-2096:
--
Attachment: SENTRY-2096.001.patch
> Fail unit tests at end
> --
>
> Key:
[
https://issues.apache.org/jira/browse/SENTRY-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284388#comment-16284388
]
Na Li commented on SENTRY-2096:
---
mvn test --fail-at-end should be used in test-patch.py
> Fail unit tests
Na Li created SENTRY-2096:
-
Summary: Fail unit tests at end
Key: SENTRY-2096
URL: https://issues.apache.org/jira/browse/SENTRY-2096
Project: Sentry
Issue Type: Task
Components: Sentry
Na Li created SENTRY-2095:
-
Summary: Support User-based privilege at Name Node through HDFS
sync
Key: SENTRY-2095
URL: https://issues.apache.org/jira/browse/SENTRY-2095
Project: Sentry
Issue Type:
[
https://issues.apache.org/jira/browse/SENTRY-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li resolved SENTRY-2083.
---
Resolution: Won't Fix
no need to do so.
> Add more test cases for policy processor
>
[
https://issues.apache.org/jira/browse/SENTRY-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-2091:
--
Attachment: SENTRY-2091.003.patch
v3. fix hive test failure.
> User-based Privilege is broken by SENTRY-769
>
[
https://issues.apache.org/jira/browse/SENTRY-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-2091:
--
Attachment: SENTRY-2091.002.patch
v2. fix solr test failure
> User-based Privilege is broken by SENTRY-769
>
[
https://issues.apache.org/jira/browse/SENTRY-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-2091:
--
Status: Patch Available (was: Open)
> User-based Privilege is broken by SENTRY-769
>
[
https://issues.apache.org/jira/browse/SENTRY-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-2091:
--
Attachment: SENTRY-2091.001.patch
> User-based Privilege is broken by SENTRY-769
>
[
https://issues.apache.org/jira/browse/SENTRY-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-2092:
--
Attachment: SENTRY-2092.002.patch
v2. update error message
> Drop Role log message shows "Creating role"
>
[
https://issues.apache.org/jira/browse/SENTRY-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-2092:
--
Attachment: SENTRY-2092.001.patch
> Drop Role log message shows "Creating role"
>
[
https://issues.apache.org/jira/browse/SENTRY-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-2092:
--
Status: Patch Available (was: Open)
> Drop Role log message shows "Creating role"
>
Na Li created SENTRY-2092:
-
Summary: Drop Role log message shows "Creating role"
Key: SENTRY-2092
URL: https://issues.apache.org/jira/browse/SENTRY-2092
Project: Sentry
Issue Type: Bug
Na Li created SENTRY-2091:
-
Summary: User-based Privilege is broken by SENTRY-769
Key: SENTRY-2091
URL: https://issues.apache.org/jira/browse/SENTRY-2091
Project: Sentry
Issue Type: Bug
Na Li created SENTRY-2083:
-
Summary: Add more test cases for policy processor
Key: SENTRY-2083
URL: https://issues.apache.org/jira/browse/SENTRY-2083
Project: Sentry
Issue Type: Task
[
https://issues.apache.org/jira/browse/SENTRY-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li resolved SENTRY-1813.
---
Resolution: Duplicate
Fix Version/s: (was: 2.1.0)
2.0.0
> LeaderStatusMonitor
[
https://issues.apache.org/jira/browse/SENTRY-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-2070:
--
Resolution: Won't Fix
Status: Resolved (was: Patch Available)
The corresponding test does not fail.
[
https://issues.apache.org/jira/browse/SENTRY-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16271654#comment-16271654
]
Na Li commented on SENTRY-2079:
---
[~spena] Is this related to SENTRY-1813?
> Sentry HA leader monitor does
[
https://issues.apache.org/jira/browse/SENTRY-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li resolved SENTRY-379.
--
Resolution: Fixed
test shows the DB name is captured when firing failurehook.
> Db entities are not captured
[
https://issues.apache.org/jira/browse/SENTRY-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267026#comment-16267026
]
Na Li commented on SENTRY-379:
--
[~spena] [~kkalyan] I believe this is fixed. And test
[
https://issues.apache.org/jira/browse/SENTRY-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-2070:
--
Attachment: SENTRY-2070.001.patch
> TestSentryShellSolr tests are case sensitive to privileges
>
[
https://issues.apache.org/jira/browse/SENTRY-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-2070:
--
Status: Patch Available (was: Open)
> TestSentryShellSolr tests are case sensitive to privileges
>
Na Li created SENTRY-2070:
-
Summary: TestSentryShellSolr tests are case sensitive to privileges
Key: SENTRY-2070
URL: https://issues.apache.org/jira/browse/SENTRY-2070
Project: Sentry
Issue Type:
[
https://issues.apache.org/jira/browse/SENTRY-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-2024:
--
Attachment: SENTRY-2024.005.patch
v5. Make index name easier to read
> Drop Index that includes
[
https://issues.apache.org/jira/browse/SENTRY-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-2024:
--
Attachment: SENTRY-2024.004.patch
v4. Create index for snapshot ID
> Drop Index that includes AUTHZ_OBJ_NAME
[
https://issues.apache.org/jira/browse/SENTRY-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-2024:
--
Attachment: SENTRY-2024.003.patch
v3. drop index that contains the AUTHZ_OBJ_NAME
> Drop Index that includes
[
https://issues.apache.org/jira/browse/SENTRY-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-2024:
--
Description:
AUTHZ_OBJ_NAME has (384) chars. It is constructed by sentry from notification
event as
[
https://issues.apache.org/jira/browse/SENTRY-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-2024:
--
Summary: Drop Index that includes AUTHZ_OBJ_NAME (was: Specify Char Set
for AUTHZ_OBJ_NAME)
> Drop Index
[
https://issues.apache.org/jira/browse/SENTRY-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16261670#comment-16261670
]
Na Li commented on SENTRY-2024:
---
I am OK to drop this index, so we don't have issue for MySql server. I
[
https://issues.apache.org/jira/browse/SENTRY-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-2066:
--
Attachment: SENTRY-2066.003.patch
v3. Simplify logic and remove local variable isDBSet
> DB name is not set
[
https://issues.apache.org/jira/browse/SENTRY-2067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16261473#comment-16261473
]
Na Li commented on SENTRY-2067:
---
If the notification table is empty, we should get a full snapshot even
[
https://issues.apache.org/jira/browse/SENTRY-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16261144#comment-16261144
]
Na Li commented on SENTRY-2024:
---
[~spena] getMAuthzPathsMappingCore() is to get he paths associated with a
[
https://issues.apache.org/jira/browse/SENTRY-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16261085#comment-16261085
]
Na Li commented on SENTRY-2065:
---
We can make DB to assign the timestamps in all entries saved in sentry DB.
[
https://issues.apache.org/jira/browse/SENTRY-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-2066:
--
Attachment: SENTRY-2066.002.patch
v2. make error message in test more meaningful
> DB name is not set for
[
https://issues.apache.org/jira/browse/SENTRY-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16261047#comment-16261047
]
Na Li commented on SENTRY-2064:
---
The proposed Thrift changes
const string UNUSED_TIME_DATASTORE =
[
https://issues.apache.org/jira/browse/SENTRY-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16261047#comment-16261047
]
Na Li edited comment on SENTRY-2064 at 11/21/17 4:59 PM:
-
The proposed Thrift
[
https://issues.apache.org/jira/browse/SENTRY-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-2064:
--
Description:
When sentry server sends response to HDFS, it includes the timestamp of the
current time at the
[
https://issues.apache.org/jira/browse/SENTRY-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-2066:
--
Status: Patch Available (was: Open)
> DB name is not set for AlterTable
> --
[
https://issues.apache.org/jira/browse/SENTRY-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-2066:
--
Attachment: SENTRY-2066.001.patch
> DB name is not set for AlterTable
> --
>
Na Li created SENTRY-2066:
-
Summary: DB name is not set for AlterTable
Key: SENTRY-2066
URL: https://issues.apache.org/jira/browse/SENTRY-2066
Project: Sentry
Issue Type: Bug
Components:
Na Li created SENTRY-2065:
-
Summary: Timestamp in MSentryPathChange and MSentryPermChange
should be set by DB server
Key: SENTRY-2065
URL: https://issues.apache.org/jira/browse/SENTRY-2065
Project: Sentry
Na Li created SENTRY-2064:
-
Summary: Sentry client at HDFS should send back the timestamp in
last response
Key: SENTRY-2064
URL: https://issues.apache.org/jira/browse/SENTRY-2064
Project: Sentry
Na Li created SENTRY-2063:
-
Summary: Add timestamp in Thrift API for HDFS integration
Key: SENTRY-2063
URL: https://issues.apache.org/jira/browse/SENTRY-2063
Project: Sentry
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/SENTRY-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259569#comment-16259569
]
Na Li commented on SENTRY-2024:
---
[~spena] MySql 5.7.20 does not have this issue. So MySql server version
[
https://issues.apache.org/jira/browse/SENTRY-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257795#comment-16257795
]
Na Li commented on SENTRY-2024:
---
[~spena] This is test on 5.5.56-MariaDB, and it also failed to create the
[
https://issues.apache.org/jira/browse/SENTRY-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257608#comment-16257608
]
Na Li commented on SENTRY-1572:
---
[~xinrantinney] I think the reason the code load class is to avoid
[
https://issues.apache.org/jira/browse/SENTRY-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-1964:
--
Resolution: Won't Fix
Status: Resolved (was: Patch Available)
This approach does not work in some
[
https://issues.apache.org/jira/browse/SENTRY-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16256448#comment-16256448
]
Na Li commented on SENTRY-1964:
---
[~akolb] the only problem is the scenario that the table location is
[
https://issues.apache.org/jira/browse/SENTRY-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16256443#comment-16256443
]
Na Li commented on SENTRY-1964:
---
The problem is to find the authObj from path.
For example, with the code
[
https://issues.apache.org/jira/browse/SENTRY-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li reassigned SENTRY-2051:
-
Assignee: (was: Na Li)
> Catch SentryGroupNotFoundException in thrift server handler
>
[
https://issues.apache.org/jira/browse/SENTRY-2046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16254546#comment-16254546
]
Na Li commented on SENTRY-2046:
---
We should get full snapshot when sentryStore.isAuthzPathsMappingEmpty()
[
https://issues.apache.org/jira/browse/SENTRY-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-2041:
--
Resolution: Won't Fix
Fix Version/s: 2.0.0
Status: Resolved (was: Patch Available)
> Change
[
https://issues.apache.org/jira/browse/SENTRY-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-1894:
--
Resolution: Won't Fix
Status: Resolved (was: Patch Available)
SENTRY-2028 does not add dataNucleus
[
https://issues.apache.org/jira/browse/SENTRY-1922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16254248#comment-16254248
]
Na Li commented on SENTRY-1922:
---
[~kkalyan] We can move it to a release after 2.0.0. We still want to have
801 - 900 of 1401 matches
Mail list logo
