[jira] [Updated] (AMBARI-24808) Logs are not showing in Hiveview2 for hive query.
[ https://issues.apache.org/jira/browse/AMBARI-24808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-24808: --- Resolution: Fixed Status: Resolved (was: Patch Available) merged in branch-2.6 > Logs are not showing in Hiveview2 for hive query. > - > > Key: AMBARI-24808 > URL: https://issues.apache.org/jira/browse/AMBARI-24808 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.6.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore >Priority: Major > Labels: pull-request-available > Time Spent: 1h 10m > Remaining Estimate: 0h > > Sometimes the logs in hive view does not show. This happens frequently for > Hive interactive queries. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24808) Logs are not showing in Hiveview2 for hive query.
[ https://issues.apache.org/jira/browse/AMBARI-24808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-24808: --- Status: Patch Available (was: Open) pull request created : https://github.com/apache/ambari/pull/2495 > Logs are not showing in Hiveview2 for hive query. > - > > Key: AMBARI-24808 > URL: https://issues.apache.org/jira/browse/AMBARI-24808 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.6.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore >Priority: Major > > Sometimes the logs in hive view does not show. This happens frequently for > Hive interactive queries. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24808) Logs are not showing in Hiveview2 for hive query.
[ https://issues.apache.org/jira/browse/AMBARI-24808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16658987#comment-16658987 ] Nitiraj Singh Rathore commented on AMBARI-24808: Most probably this was because the poll period between log fetch query from hive view back end to hive server was 5 secs. And the statement gets executed before this period. I have corrected the logic and made it fail proof in case of multiple and small queries. This seems to be work. will submit my changes. > Logs are not showing in Hiveview2 for hive query. > - > > Key: AMBARI-24808 > URL: https://issues.apache.org/jira/browse/AMBARI-24808 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.6.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore >Priority: Major > > Sometimes the logs in hive view does not show. This happens frequently for > Hive interactive queries. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24808) Logs are not showing in Hiveview2 for hive query.
Nitiraj Singh Rathore created AMBARI-24808: -- Summary: Logs are not showing in Hiveview2 for hive query. Key: AMBARI-24808 URL: https://issues.apache.org/jira/browse/AMBARI-24808 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.6.0 Reporter: Nitiraj Singh Rathore Assignee: Nitiraj Singh Rathore Sometimes the logs in hive view does not show. This happens frequently for Hive interactive queries. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24783) Cleanup dependencies in Capacity Scheduler
[ https://issues.apache.org/jira/browse/AMBARI-24783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-24783: --- Resolution: Fixed Status: Resolved (was: Patch Available) merged into branch-2.7 and trunk > Cleanup dependencies in Capacity Scheduler > -- > > Key: AMBARI-24783 > URL: https://issues.apache.org/jira/browse/AMBARI-24783 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.7.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 2h 40m > Remaining Estimate: 0h > > remove any dependencies with probable bugs in it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24783) Cleanup dependencies in Capacity Scheduler
[ https://issues.apache.org/jira/browse/AMBARI-24783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-24783: --- Status: Patch Available (was: Open) submitted pull request with exclusion of security affected lib in all views > Cleanup dependencies in Capacity Scheduler > -- > > Key: AMBARI-24783 > URL: https://issues.apache.org/jira/browse/AMBARI-24783 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.7.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > remove any dependencies with probable bugs in it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24783) Cleanup dependencies in Capacity Scheduler
[ https://issues.apache.org/jira/browse/AMBARI-24783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16655599#comment-16655599 ] Nitiraj Singh Rathore commented on AMBARI-24783: Unfortunately, other views are also plagued with same error. I just checked now. Changes in all the views can be covered under this but itself. > Cleanup dependencies in Capacity Scheduler > -- > > Key: AMBARI-24783 > URL: https://issues.apache.org/jira/browse/AMBARI-24783 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.7.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > remove any dependencies with probable bugs in it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (AMBARI-24783) Cleanup dependencies in Capacity Scheduler
[ https://issues.apache.org/jira/browse/AMBARI-24783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16655599#comment-16655599 ] Nitiraj Singh Rathore edited comment on AMBARI-24783 at 10/18/18 5:07 PM: -- Unfortunately, other views are also plagued with same dependencies. I just checked now. Changes in all the views can be covered under this but itself. was (Author: nitiraj.rathore): Unfortunately, other views are also plagued with same error. I just checked now. Changes in all the views can be covered under this but itself. > Cleanup dependencies in Capacity Scheduler > -- > > Key: AMBARI-24783 > URL: https://issues.apache.org/jira/browse/AMBARI-24783 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.7.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > remove any dependencies with probable bugs in it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24783) Cleanup dependencies in Capacity Scheduler
[ https://issues.apache.org/jira/browse/AMBARI-24783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-24783: --- Description: remove any dependencies with probable bugs in it. > Cleanup dependencies in Capacity Scheduler > -- > > Key: AMBARI-24783 > URL: https://issues.apache.org/jira/browse/AMBARI-24783 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.7.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 20m > Remaining Estimate: 0h > > remove any dependencies with probable bugs in it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24783) Cleanup dependencies in Capacity Scheduler
[ https://issues.apache.org/jira/browse/AMBARI-24783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-24783: --- Summary: Cleanup dependencies in Capacity Scheduler (was: Remove dependency on org.eclipse.jetty:jetty-http:jar:9.3.19.v20170502 in Capacity Scheduler) > Cleanup dependencies in Capacity Scheduler > -- > > Key: AMBARI-24783 > URL: https://issues.apache.org/jira/browse/AMBARI-24783 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.7.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore >Priority: Major > Fix For: 2.7.3 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24783) Remove dependency on org.eclipse.jetty:jetty-http:jar:9.3.19.v20170502 in Capacity Scheduler
Nitiraj Singh Rathore created AMBARI-24783: -- Summary: Remove dependency on org.eclipse.jetty:jetty-http:jar:9.3.19.v20170502 in Capacity Scheduler Key: AMBARI-24783 URL: https://issues.apache.org/jira/browse/AMBARI-24783 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.7.0 Reporter: Nitiraj Singh Rathore Assignee: Nitiraj Singh Rathore Fix For: 2.7.3 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24535) File View not accessible in Ambari 2.7 after enabling 3 namenodes in HDP 3.0
[
https://issues.apache.org/jira/browse/AMBARI-24535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nitiraj Singh Rathore updated AMBARI-24535:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> File View not accessible in Ambari 2.7 after enabling 3 namenodes in HDP 3.0
>
>
> Key: AMBARI-24535
> URL: https://issues.apache.org/jira/browse/AMBARI-24535
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.7.0
>Reporter: Akhil S Naik
>Assignee: Nitiraj Singh Rathore
>Priority: Major
> Labels: pull-request-available
> Time Spent: 3h
> Remaining Estimate: 0h
>
> *Ambari-2.7.0* supports HDFS Federation architecture
> But if we configure 3 namenode the Files view never works.
> It will fail with below exception
> {code:java}
> Service 'hdfs' check failed: HDFS080 webhdfs.ha.namenodes.list namenodes
> count is not exactly 2
> Service 'hdfs' check failed:
> org.apache.ambari.view.utils.hdfs.HdfsApiException: HDFS080
> webhdfs.ha.namenodes.list namenodes count is not exactly 2
> at
> org.apache.ambari.view.utils.hdfs.ConfigurationBuilder.copyHAProperties(ConfigurationBuilder.java:247)
>
> at
> org.apache.ambari.view.utils.hdfs.ConfigurationBuilder.parseProperties(ConfigurationBuilder.java:110)
>
> at
> org.apache.ambari.view.utils.hdfs.ConfigurationBuilder.buildConfig(ConfigurationBuilder.java:327)
>
> at org.apache.ambari.view.utils.hdfs.HdfsApi.(HdfsApi.java:75)
> at org.apache.ambari.view.utils.hdfs.HdfsUtil.getHdfsApi(HdfsUtil.java:157)
> at
> org.apache.ambari.view.utils.hdfs.HdfsUtil.connectToHDFSApi(HdfsUtil.java:145)
>
> at
> org.apache.ambari.view.commons.hdfs.HdfsService.hdfsSmokeTest(HdfsService.java:145)
>
> at
> org.apache.ambari.view.filebrowser.HelpService.hdfsStatus(HelpService.java:95)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
>
> {code}
> By inspecting the code , it looks like this is not supposed to work in
> filesview and it wil only allow two namenodes
> code :
> https://github.com/apache/ambari/blob/trunk/contrib/views/utils/src/main/java/org/apache/ambari/view/utils/hdfs/ConfigurationBuilder.java#L247
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24535) File View not accessible in Ambari 2.7 after enabling 3 namenodes in HDP 3.0
[
https://issues.apache.org/jira/browse/AMBARI-24535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16628261#comment-16628261
]
Nitiraj Singh Rathore commented on AMBARI-24535:
Changes have been merged and should be available in next ambari release
> File View not accessible in Ambari 2.7 after enabling 3 namenodes in HDP 3.0
>
>
> Key: AMBARI-24535
> URL: https://issues.apache.org/jira/browse/AMBARI-24535
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.7.0
>Reporter: Akhil S Naik
>Assignee: Nitiraj Singh Rathore
>Priority: Major
> Labels: pull-request-available
> Time Spent: 3h
> Remaining Estimate: 0h
>
> *Ambari-2.7.0* supports HDFS Federation architecture
> But if we configure 3 namenode the Files view never works.
> It will fail with below exception
> {code:java}
> Service 'hdfs' check failed: HDFS080 webhdfs.ha.namenodes.list namenodes
> count is not exactly 2
> Service 'hdfs' check failed:
> org.apache.ambari.view.utils.hdfs.HdfsApiException: HDFS080
> webhdfs.ha.namenodes.list namenodes count is not exactly 2
> at
> org.apache.ambari.view.utils.hdfs.ConfigurationBuilder.copyHAProperties(ConfigurationBuilder.java:247)
>
> at
> org.apache.ambari.view.utils.hdfs.ConfigurationBuilder.parseProperties(ConfigurationBuilder.java:110)
>
> at
> org.apache.ambari.view.utils.hdfs.ConfigurationBuilder.buildConfig(ConfigurationBuilder.java:327)
>
> at org.apache.ambari.view.utils.hdfs.HdfsApi.(HdfsApi.java:75)
> at org.apache.ambari.view.utils.hdfs.HdfsUtil.getHdfsApi(HdfsUtil.java:157)
> at
> org.apache.ambari.view.utils.hdfs.HdfsUtil.connectToHDFSApi(HdfsUtil.java:145)
>
> at
> org.apache.ambari.view.commons.hdfs.HdfsService.hdfsSmokeTest(HdfsService.java:145)
>
> at
> org.apache.ambari.view.filebrowser.HelpService.hdfsStatus(HelpService.java:95)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
>
> {code}
> By inspecting the code , it looks like this is not supposed to work in
> filesview and it wil only allow two namenodes
> code :
> https://github.com/apache/ambari/blob/trunk/contrib/views/utils/src/main/java/org/apache/ambari/view/utils/hdfs/ConfigurationBuilder.java#L247
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24535) File View not accessible in Ambari 2.7 after enabling 3 namenodes in HDP 3.0
[
https://issues.apache.org/jira/browse/AMBARI-24535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nitiraj Singh Rathore updated AMBARI-24535:
---
Assignee: Nitiraj Singh Rathore
Status: Patch Available (was: Open)
Instead of hardcoded 2 namenodes, configurations now accept list of comma
separated namenode urls.
Manual testing done on 3 namenode cluster. Also test cases updated.
Submitted PR :
https://github.com/apache/ambari/pull/2351
https://github.com/apache/ambari/pull/2352
> File View not accessible in Ambari 2.7 after enabling 3 namenodes in HDP 3.0
>
>
> Key: AMBARI-24535
> URL: https://issues.apache.org/jira/browse/AMBARI-24535
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.7.0
>Reporter: Akhil S Naik
>Assignee: Nitiraj Singh Rathore
>Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> *Ambari-2.7.0* supports HDFS Federation architecture
> But if we configure 3 namenode the Files view never works.
> It will fail with below exception
> {code:java}
> Service 'hdfs' check failed: HDFS080 webhdfs.ha.namenodes.list namenodes
> count is not exactly 2
> Service 'hdfs' check failed:
> org.apache.ambari.view.utils.hdfs.HdfsApiException: HDFS080
> webhdfs.ha.namenodes.list namenodes count is not exactly 2
> at
> org.apache.ambari.view.utils.hdfs.ConfigurationBuilder.copyHAProperties(ConfigurationBuilder.java:247)
>
> at
> org.apache.ambari.view.utils.hdfs.ConfigurationBuilder.parseProperties(ConfigurationBuilder.java:110)
>
> at
> org.apache.ambari.view.utils.hdfs.ConfigurationBuilder.buildConfig(ConfigurationBuilder.java:327)
>
> at org.apache.ambari.view.utils.hdfs.HdfsApi.(HdfsApi.java:75)
> at org.apache.ambari.view.utils.hdfs.HdfsUtil.getHdfsApi(HdfsUtil.java:157)
> at
> org.apache.ambari.view.utils.hdfs.HdfsUtil.connectToHDFSApi(HdfsUtil.java:145)
>
> at
> org.apache.ambari.view.commons.hdfs.HdfsService.hdfsSmokeTest(HdfsService.java:145)
>
> at
> org.apache.ambari.view.filebrowser.HelpService.hdfsStatus(HelpService.java:95)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
>
> {code}
> By inspecting the code , it looks like this is not supposed to work in
> filesview and it wil only allow two namenodes
> code :
> https://github.com/apache/ambari/blob/trunk/contrib/views/utils/src/main/java/org/apache/ambari/view/utils/hdfs/ConfigurationBuilder.java#L247
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24165) hive view : remove conflicting set statements while uploading the table
[
https://issues.apache.org/jira/browse/AMBARI-24165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nitiraj Singh Rathore resolved AMBARI-24165.
Resolution: Fixed
> hive view : remove conflicting set statements while uploading the table
> ---
>
> Key: AMBARI-24165
> URL: https://issues.apache.org/jira/browse/AMBARI-24165
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Nitiraj Singh Rathore
>Assignee: Nitiraj Singh Rathore
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.6.2
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> The following 2 set statements can give error at run time since they are
> supposed to be only set through hive-site.xml file.
> https://github.com/nitirajrathore/ambari/blob/4595bd2a239cbe4838c8eeb5410b161a3d8a7ee6/contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/internal/query/generators/InsertFromQueryGenerator.java#L51
> insertQuery.append("SET hive.support.concurrency=true;").append("\n");
> insertQuery.append("SET
> hive.txn.manager=org.apache.hadoop.hive.ql.lockmgr.DbTxnManager;").append("\n");
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23817) Visualizing the Encrypted zones and Erasure coded zones in HDFS
[ https://issues.apache.org/jira/browse/AMBARI-23817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-23817: --- Resolution: Fixed Status: Resolved (was: Patch Available) added UI rows and backend changes to show the encrypted zone and encoding > Visualizing the Encrypted zones and Erasure coded zones in HDFS > --- > > Key: AMBARI-23817 > URL: https://issues.apache.org/jira/browse/AMBARI-23817 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.2 > > Attachments: AMBARI-23817-trunk.patch > > Time Spent: 1h 50m > Remaining Estimate: 0h > > For hadoop 3.0 Files view should show whether a folder or file is Encrypted > or not and what Erasure coding policy is used for that. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24509) Security vulnerabilities with Hive view (XSS)
[ https://issues.apache.org/jira/browse/AMBARI-24509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore resolved AMBARI-24509. Resolution: Fixed UI will not accept input with javascript in its text. > Security vulnerabilities with Hive view (XSS) > - > > Key: AMBARI-24509 > URL: https://issues.apache.org/jira/browse/AMBARI-24509 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.6.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore >Priority: Major > Labels: pull-request-available > Fix For: 2.6.2 > > Time Spent: 40m > Remaining Estimate: 0h > > It is possible for an attacker to steal information or access from users by > executing malicious javascript. This is possible due to hive directly taking > data/information from events and directly populating messages, this includes > directly inserting data that contains html or javascript code. Leveraging > this one user could create a malicious message to steal access or information > of another user. Upon viewing the malicious message the vicitim would be > comprimised by directly scraping any information on the page, modify its > appearence, or having their session information stolen. > Bug reproduce steps: > 1. go to Hive view from Ambari > 2. click on 'Tables' and click on '+' to create a new table > 3. In the table name input: '""' > and add a column with name and > datatype TINYINT and click on create > 4. There is a javascript popup showing the document name and domain name -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24509) Security vulnerabilities with Hive view (XSS)
Nitiraj Singh Rathore created AMBARI-24509: -- Summary: Security vulnerabilities with Hive view (XSS) Key: AMBARI-24509 URL: https://issues.apache.org/jira/browse/AMBARI-24509 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.6.0 Reporter: Nitiraj Singh Rathore Assignee: Nitiraj Singh Rathore Fix For: 2.6.2 It is possible for an attacker to steal information or access from users by executing malicious javascript. This is possible due to hive directly taking data/information from events and directly populating messages, this includes directly inserting data that contains html or javascript code. Leveraging this one user could create a malicious message to steal access or information of another user. Upon viewing the malicious message the vicitim would be comprimised by directly scraping any information on the page, modify its appearence, or having their session information stolen. Bug reproduce steps: 1. go to Hive view from Ambari 2. click on 'Tables' and click on '+' to create a new table 3. In the table name input: '""' and add a column with name and datatype TINYINT and click on create 4. There is a javascript popup showing the document name and domain name -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24231) Adding additional jars in classpath of ambari views.
Nitiraj Singh Rathore created AMBARI-24231: -- Summary: Adding additional jars in classpath of ambari views. Key: AMBARI-24231 URL: https://issues.apache.org/jira/browse/AMBARI-24231 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.6.0 Reporter: Nitiraj Singh Rathore Assignee: Nitiraj Singh Rathore Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24165) hive view : remove conflicting set statements while uploading the table
Nitiraj Singh Rathore created AMBARI-24165:
--
Summary: hive view : remove conflicting set statements while
uploading the table
Key: AMBARI-24165
URL: https://issues.apache.org/jira/browse/AMBARI-24165
Project: Ambari
Issue Type: Bug
Affects Versions: 2.6.1
Reporter: Nitiraj Singh Rathore
Assignee: Nitiraj Singh Rathore
Fix For: 2.6.2
The following 2 set statements can give error at run time since they are
supposed to be only set through hive-site.xml file.
https://github.com/nitirajrathore/ambari/blob/4595bd2a239cbe4838c8eeb5410b161a3d8a7ee6/contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/internal/query/generators/InsertFromQueryGenerator.java#L51
insertQuery.append("SET hive.support.concurrency=true;").append("\n");
insertQuery.append("SET
hive.txn.manager=org.apache.hadoop.hive.ql.lockmgr.DbTxnManager;").append("\n");
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-23871) Removal of huetoview migration, jobs view, hawq view, storm view from ambari
[ https://issues.apache.org/jira/browse/AMBARI-23871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore resolved AMBARI-23871. Resolution: Fixed > Removal of huetoview migration, jobs view, hawq view, storm view from ambari > - > > Key: AMBARI-23871 > URL: https://issues.apache.org/jira/browse/AMBARI-23871 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > These views cannot be maintained with the new release of Ambari and needs to > be removed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23871) Removal of huetoview migration, jobs view, hawq view, storm view from ambari
[ https://issues.apache.org/jira/browse/AMBARI-23871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-23871: --- Fix Version/s: (was: 3.0.0) 2.7.0 > Removal of huetoview migration, jobs view, hawq view, storm view from ambari > - > > Key: AMBARI-23871 > URL: https://issues.apache.org/jira/browse/AMBARI-23871 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore >Priority: Major > Fix For: 2.7.0 > > > These views cannot be maintained with the new release of Ambari and needs to > be removed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23179) Hive view 2.0 does not parse the TAB delimited CSV files while using 'Upload Table'
[
https://issues.apache.org/jira/browse/AMBARI-23179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nitiraj Singh Rathore updated AMBARI-23179:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Hive view 2.0 does not parse the TAB delimited CSV files while using 'Upload
> Table'
> ---
>
> Key: AMBARI-23179
> URL: https://issues.apache.org/jira/browse/AMBARI-23179
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.6.0
> Environment: HDP 2.6.3
> Ambari 2.6.0
>Reporter: Sindhu Subhas
>Assignee: Nitiraj Singh Rathore
>Priority: Major
> Labels: pull-request-available
> Attachments: Screen Shot 2018-02-28 at 1.02.44 AM.png, Screen Shot
> 2018-02-28 at 5.05.55 PM.png, Screen Shot 2018-02-28 at 5.06.47 PM.png,
> Screen Shot 2018-02-28 at 5.07.30 PM.png, datatab.tsv
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Problem:
> When trying to Upload table from Hive view 2.0 from a TAB delimited file, the
> data is not parsed as expected.
> Same feature works as expected in Hive view 1.5.0.
> Attached output from Hive view 2.0 and output from Hive view 1.5.0.
> From the code, we do see difference in the code for
> src/main/java/org/apache/ambari/view/hive20/resources/uploads/UploadService.java.
> Debug from Hive view 2.0:
> {code:java}
> 27 Feb 2018 20:27:28,169 DEBUG
> [HiveViewActorSystem-akka.actor.default-dispatcher-4] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] OperationController:53 - } java.util.HashMap
> 27 Feb 2018 20:27:28,169 DEBUG
> [HiveViewActorSystem-akka.actor.default-dispatcher-4] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] HiveActor:41 - Message submitted:
> 927343c0-5ed6-435c-be60-37448ac1a8b0
> 27 Feb 2018 20:27:30,925 INFO [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] UploadService:484 - isFirstRowHeader : false,
> inputFileType : CSV
> 27 Feb 2018 20:27:30,934 INFO [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] OpenCSVParser:50 - setting delimiter as T
> 27 Feb 2018 20:27:30,934 INFO [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] OpenCSVParser:56 - setting Quote char : "
> 27 Feb 2018 20:27:30,934 INFO [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] OpenCSVParser:62 - setting escapeChar : \
> 27 Feb 2018 20:27:30,939 INFO [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] Parser:75 - generating preview for :
> ParseOptions{options={OPTIONS_CSV_QUOTE=", OPTIONS_CSV_DELIMITER=T,
> HEADER=NONE, FILE_TYPE=CSV, OPTIONS_CSV_ESCAPE_CHAR=\}}
> 27 Feb 2018 20:27:30,939 DEBUG [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] Parser:83 - Illegal number of preview columns supplied
> null
> 27 Feb 2018 20:27:30,943 DEBUG [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] ParseUtils:152 - error while parsing as timestamp
> string column1 column2 column3
> java.lang.IllegalArgumentException: Timestamp format must be -mm-dd
> hh:mm:ss[.f]
> at java.sql.Timestamp.valueOf(Timestamp.java:204)
> .
> 27 Feb 2018 20:27:30,948 INFO [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] Parser:149 - datatype detected for column 0 : STRING
> 27 Feb 2018 20:27:30,949 DEBUG [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] Parser:159 - return headers :
> [ColumnInfo{name='column1', type='STRING', precision=null, scale=null,
> comment='null'}]
> {code}
> Debug from Hive view 1.5.0:
> {code:java}
> 27 Feb 2018 20:13:15,881 INFO [ambari-client-thread-38] [HIVE 1.5.0
> AUTO_HIVE_INSTANCE] UploadService:499 - isFirstRowHeader : true,
> inputFileType : CSV
> 27 Feb 2018 20:13:15,918 INFO [ambari-client-thread-38] [HIVE 1.5.0
> AUTO_HIVE_INSTANCE] OpenCSVParser:50 - setting delimiter as
> 27 Feb 2018 20:13:15,919 INFO [ambari-client-thread-38] [HIVE 1.5.0
> AUTO_HIVE_INSTANCE] OpenCSVParser:56 - setting Quote char : "
> 27 Feb 2018 20:13:15,919 INFO [ambari-client-thread-38] [HIVE 1.5.0
> AUTO_HIVE_INSTANCE] OpenCSVParser:62 - setting escapeChar : \
> 27 Feb 2018 20:13:15,928 INFO [ambari-client-thread-38] [HIVE 1.5.0
> AUTO_HIVE_INSTANCE] Parser:75 - generating preview for :
> ParseOptions{options={OPTIONS_CSV_QUOTE=", OPTIONS_CSV_DELIMITER= ,
> HEADER=FIRST_RECORD, FILE_TYPE=CSV, OPTIONS_CSV_ESCAPE_CHAR=\}}
> 27 Feb 2018 20:13:15,929 DEBUG [ambari-client-thread-38] [HIVE 1.5.0
> AUTO_HIVE_INSTANCE] Parser:83 - Illegal number of preview columns supplied
> null
> 27 Feb 2018 20:13:15,936 DEBUG [ambari-client-thread-38] [HIVE 1.5.0
> AUTO_HIVE_INSTANCE] ParseUtils:152 - error while parsing as timestamp string
> AD
> java.lang.IllegalArgumentException: Timestamp format must be -mm-dd
> hh:mm:ss[.fff
[jira] [Updated] (AMBARI-23604) ParseException line 1:116 mismatched input 'ROW' expecting INTO near ')' in table buckets specification when uploading table using Hive view 2.0.
[
https://issues.apache.org/jira/browse/AMBARI-23604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nitiraj Singh Rathore updated AMBARI-23604:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> ParseException line 1:116 mismatched input 'ROW' expecting INTO near ')' in
> table buckets specification when uploading table using Hive view 2.0.
> -
>
> Key: AMBARI-23604
> URL: https://issues.apache.org/jira/browse/AMBARI-23604
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.6.1
> Environment: HDP 2.6.3
> Ambari 2.6.1
>Reporter: Sindhu Subhas
>Assignee: Nitiraj Singh Rathore
>Priority: Critical
> Labels: pull-request-available
> Attachments: test_csv.csv
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> *Problem:*
> When uploading table using CSV file as transactional table, below is the
> error see:
> {code:java}
> java.lang.Exception: org.apache.hive.service.cli.HiveSQLException: Error
> while compiling statement: FAILED: ParseException line 1:116 mismatched input
> 'ROW' expecting INTO near ')' in table buckets specification
> java.lang.Exception: org.apache.hive.service.cli.HiveSQLException: Error
> while compiling statement: FAILED: ParseException line 1:116 mismatched input
> 'ROW' expecting INTO near ')' in table buckets specification
> at
> org.apache.ambari.view.hive20.resources.jobs.JobService.getOne(JobService.java:147)
> at sun.reflect.GeneratedMethodAccessor831.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> {code}
> *Steps to replicate:*
> 1. Upload the attached file.
> 2. Select any of the columns as 'clustered'.
> 3. Under Advanced options, enable transactional and buckets=4.
> 4. Click on create table.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23817) Visualizing the Encrypted zones and Erasure coded zones in HDFS
[ https://issues.apache.org/jira/browse/AMBARI-23817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-23817: --- Attachment: AMBARI-23817-trunk.patch > Visualizing the Encrypted zones and Erasure coded zones in HDFS > --- > > Key: AMBARI-23817 > URL: https://issues.apache.org/jira/browse/AMBARI-23817 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore >Priority: Critical > Fix For: 2.7.0 > > Attachments: AMBARI-23817-trunk.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > For hadoop 3.0 Files view should show whether a folder or file is Encrypted > or not and what Erasure coding policy is used for that. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23817) Visualizing the Encrypted zones and Erasure coded zones in HDFS
[ https://issues.apache.org/jira/browse/AMBARI-23817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-23817: --- Labels: (was: pull-request-available) Status: Patch Available (was: Open) > Visualizing the Encrypted zones and Erasure coded zones in HDFS > --- > > Key: AMBARI-23817 > URL: https://issues.apache.org/jira/browse/AMBARI-23817 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore >Priority: Critical > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > For hadoop 3.0 Files view should show whether a folder or file is Encrypted > or not and what Erasure coding policy is used for that. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23817) Visualizing the Encrypted zones and Erasure coded zones in HDFS
[ https://issues.apache.org/jira/browse/AMBARI-23817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16478656#comment-16478656 ] Nitiraj Singh Rathore commented on AMBARI-23817: Previous pull request got reverted because of unavailability of release of hadoop that is required in views. Uploading the patch for the changes with expected Hadoop release 3.1.1. > Visualizing the Encrypted zones and Erasure coded zones in HDFS > --- > > Key: AMBARI-23817 > URL: https://issues.apache.org/jira/browse/AMBARI-23817 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore >Priority: Critical > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > For hadoop 3.0 Files view should show whether a folder or file is Encrypted > or not and what Erasure coding policy is used for that. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23871) Removal of huetoview migration, jobs view, hawq view, storm view from ambari
Nitiraj Singh Rathore created AMBARI-23871: -- Summary: Removal of huetoview migration, jobs view, hawq view, storm view from ambari Key: AMBARI-23871 URL: https://issues.apache.org/jira/browse/AMBARI-23871 Project: Ambari Issue Type: Bug Components: ambari-views Reporter: Nitiraj Singh Rathore Assignee: Nitiraj Singh Rathore Fix For: 3.0.0 These views cannot be maintained with the new release of Ambari and needs to be removed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23604) ParseException line 1:116 mismatched input 'ROW' expecting INTO near ')' in table buckets specification when uploading table using Hive view 2.0.
[
https://issues.apache.org/jira/browse/AMBARI-23604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nitiraj Singh Rathore updated AMBARI-23604:
---
Status: Patch Available (was: Open)
submitted pull request.
> ParseException line 1:116 mismatched input 'ROW' expecting INTO near ')' in
> table buckets specification when uploading table using Hive view 2.0.
> -
>
> Key: AMBARI-23604
> URL: https://issues.apache.org/jira/browse/AMBARI-23604
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.6.1
> Environment: HDP 2.6.3
> Ambari 2.6.1
>Reporter: Sindhu Subhas
>Assignee: Nitiraj Singh Rathore
>Priority: Critical
> Labels: pull-request-available
> Attachments: test_csv.csv
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> *Problem:*
> When uploading table using CSV file as transactional table, below is the
> error see:
> {code:java}
> java.lang.Exception: org.apache.hive.service.cli.HiveSQLException: Error
> while compiling statement: FAILED: ParseException line 1:116 mismatched input
> 'ROW' expecting INTO near ')' in table buckets specification
> java.lang.Exception: org.apache.hive.service.cli.HiveSQLException: Error
> while compiling statement: FAILED: ParseException line 1:116 mismatched input
> 'ROW' expecting INTO near ')' in table buckets specification
> at
> org.apache.ambari.view.hive20.resources.jobs.JobService.getOne(JobService.java:147)
> at sun.reflect.GeneratedMethodAccessor831.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> {code}
> *Steps to replicate:*
> 1. Upload the attached file.
> 2. Select any of the columns as 'clustered'.
> 3. Under Advanced options, enable transactional and buckets=4.
> 4. Click on create table.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23817) Visualizing the Encrypted zones and Erasure coded zones in HDFS
[ https://issues.apache.org/jira/browse/AMBARI-23817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-23817: --- Description: For hadoop 3.0 Files view should show whether a folder or file is Encrypted or not and what Erasure coding policy is used for that. > Visualizing the Encrypted zones and Erasure coded zones in HDFS > --- > > Key: AMBARI-23817 > URL: https://issues.apache.org/jira/browse/AMBARI-23817 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore >Priority: Critical > Fix For: 2.7.0 > > > For hadoop 3.0 Files view should show whether a folder or file is Encrypted > or not and what Erasure coding policy is used for that. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23817) Visualizing the Encrypted zones and Erasure coded zones in HDFS
Nitiraj Singh Rathore created AMBARI-23817: -- Summary: Visualizing the Encrypted zones and Erasure coded zones in HDFS Key: AMBARI-23817 URL: https://issues.apache.org/jira/browse/AMBARI-23817 Project: Ambari Issue Type: Bug Components: ambari-views Reporter: Nitiraj Singh Rathore Assignee: Nitiraj Singh Rathore Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-23604) ParseException line 1:116 mismatched input 'ROW' expecting INTO near ')' in table buckets specification when uploading table using Hive view 2.0.
[
https://issues.apache.org/jira/browse/AMBARI-23604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nitiraj Singh Rathore reassigned AMBARI-23604:
--
Assignee: Nitiraj Singh Rathore
> ParseException line 1:116 mismatched input 'ROW' expecting INTO near ')' in
> table buckets specification when uploading table using Hive view 2.0.
> -
>
> Key: AMBARI-23604
> URL: https://issues.apache.org/jira/browse/AMBARI-23604
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.6.1
> Environment: HDP 2.6.3
> Ambari 2.6.1
>Reporter: Sindhu Subhas
>Assignee: Nitiraj Singh Rathore
>Priority: Critical
> Attachments: test_csv.csv
>
>
> *Problem:*
> When uploading table using CSV file as transactional table, below is the
> error see:
> {code:java}
> java.lang.Exception: org.apache.hive.service.cli.HiveSQLException: Error
> while compiling statement: FAILED: ParseException line 1:116 mismatched input
> 'ROW' expecting INTO near ')' in table buckets specification
> java.lang.Exception: org.apache.hive.service.cli.HiveSQLException: Error
> while compiling statement: FAILED: ParseException line 1:116 mismatched input
> 'ROW' expecting INTO near ')' in table buckets specification
> at
> org.apache.ambari.view.hive20.resources.jobs.JobService.getOne(JobService.java:147)
> at sun.reflect.GeneratedMethodAccessor831.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> {code}
> *Steps to replicate:*
> 1. Upload the attached file.
> 2. Select any of the columns as 'clustered'.
> 3. Under Advanced options, enable transactional and buckets=4.
> 4. Click on create table.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23294) Ambari Files view throws 500 ERROR while trying to upload/download to/from HDFS encrypted zone
[ https://issues.apache.org/jira/browse/AMBARI-23294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-23294: --- Resolution: Fixed Status: Resolved (was: Patch Available) committed patch to branch-2.6 and trunk. > Ambari Files view throws 500 ERROR while trying to upload/download to/from > HDFS encrypted zone > -- > > Key: AMBARI-23294 > URL: https://issues.apache.org/jira/browse/AMBARI-23294 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore >Priority: Major > Labels: pull-request-available > Fix For: trunk, 2.6.2 > > Time Spent: 1h > Remaining Estimate: 0h > > The problem is that the error does not show up properly on UI. > So it becomes difficult to understand. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23294) Ambari Files view throws 500 ERROR while trying to upload/download to/from HDFS encrypted zone
[ https://issues.apache.org/jira/browse/AMBARI-23294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-23294: --- Status: Patch Available (was: Open) > Ambari Files view throws 500 ERROR while trying to upload/download to/from > HDFS encrypted zone > -- > > Key: AMBARI-23294 > URL: https://issues.apache.org/jira/browse/AMBARI-23294 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore >Priority: Major > Labels: pull-request-available > Fix For: trunk, 2.6.2 > > Time Spent: 20m > Remaining Estimate: 0h > > The problem is that the error does not show up properly on UI. > So it becomes difficult to understand. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23294) Ambari Files view throws 500 ERROR while trying to upload/download to/from HDFS encrypted zone
[ https://issues.apache.org/jira/browse/AMBARI-23294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-23294: --- Summary: Ambari Files view throws 500 ERROR while trying to upload/download to/from HDFS encrypted zone (was: Ambari view throws 500 ERROR while trying to upload/download to/from HDFS encrypted zone) > Ambari Files view throws 500 ERROR while trying to upload/download to/from > HDFS encrypted zone > -- > > Key: AMBARI-23294 > URL: https://issues.apache.org/jira/browse/AMBARI-23294 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore >Priority: Major > Fix For: trunk, 2.6.2 > > > The problem is that the error does not show up properly on UI. > So it becomes difficult to understand. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23294) Ambari view throws 500 ERROR while trying to upload/download to/from HDFS encrypted zone
Nitiraj Singh Rathore created AMBARI-23294: -- Summary: Ambari view throws 500 ERROR while trying to upload/download to/from HDFS encrypted zone Key: AMBARI-23294 URL: https://issues.apache.org/jira/browse/AMBARI-23294 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.1 Reporter: Nitiraj Singh Rathore Assignee: Nitiraj Singh Rathore Fix For: trunk, 2.6.2 The problem is that the error does not show up properly on UI. So it becomes difficult to understand. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23179) Hive view 2.0 does not parse the TAB delimited CSV files while using 'Upload Table'
[
https://issues.apache.org/jira/browse/AMBARI-23179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nitiraj Singh Rathore updated AMBARI-23179:
---
Status: Patch Available (was: Open)
> Hive view 2.0 does not parse the TAB delimited CSV files while using 'Upload
> Table'
> ---
>
> Key: AMBARI-23179
> URL: https://issues.apache.org/jira/browse/AMBARI-23179
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.6.0
> Environment: HDP 2.6.3
> Ambari 2.6.0
>Reporter: Sindhu Subhas
>Assignee: Nitiraj Singh Rathore
>Priority: Major
> Labels: pull-request-available
> Attachments: Screen Shot 2018-02-28 at 1.02.44 AM.png, Screen Shot
> 2018-02-28 at 5.05.55 PM.png, Screen Shot 2018-02-28 at 5.06.47 PM.png,
> Screen Shot 2018-02-28 at 5.07.30 PM.png, datatab.tsv
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Problem:
> When trying to Upload table from Hive view 2.0 from a TAB delimited file, the
> data is not parsed as expected.
> Same feature works as expected in Hive view 1.5.0.
> Attached output from Hive view 2.0 and output from Hive view 1.5.0.
> From the code, we do see difference in the code for
> src/main/java/org/apache/ambari/view/hive20/resources/uploads/UploadService.java.
> Debug from Hive view 2.0:
> {code:java}
> 27 Feb 2018 20:27:28,169 DEBUG
> [HiveViewActorSystem-akka.actor.default-dispatcher-4] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] OperationController:53 - } java.util.HashMap
> 27 Feb 2018 20:27:28,169 DEBUG
> [HiveViewActorSystem-akka.actor.default-dispatcher-4] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] HiveActor:41 - Message submitted:
> 927343c0-5ed6-435c-be60-37448ac1a8b0
> 27 Feb 2018 20:27:30,925 INFO [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] UploadService:484 - isFirstRowHeader : false,
> inputFileType : CSV
> 27 Feb 2018 20:27:30,934 INFO [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] OpenCSVParser:50 - setting delimiter as T
> 27 Feb 2018 20:27:30,934 INFO [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] OpenCSVParser:56 - setting Quote char : "
> 27 Feb 2018 20:27:30,934 INFO [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] OpenCSVParser:62 - setting escapeChar : \
> 27 Feb 2018 20:27:30,939 INFO [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] Parser:75 - generating preview for :
> ParseOptions{options={OPTIONS_CSV_QUOTE=", OPTIONS_CSV_DELIMITER=T,
> HEADER=NONE, FILE_TYPE=CSV, OPTIONS_CSV_ESCAPE_CHAR=\}}
> 27 Feb 2018 20:27:30,939 DEBUG [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] Parser:83 - Illegal number of preview columns supplied
> null
> 27 Feb 2018 20:27:30,943 DEBUG [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] ParseUtils:152 - error while parsing as timestamp
> string column1 column2 column3
> java.lang.IllegalArgumentException: Timestamp format must be -mm-dd
> hh:mm:ss[.f]
> at java.sql.Timestamp.valueOf(Timestamp.java:204)
> .
> 27 Feb 2018 20:27:30,948 INFO [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] Parser:149 - datatype detected for column 0 : STRING
> 27 Feb 2018 20:27:30,949 DEBUG [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] Parser:159 - return headers :
> [ColumnInfo{name='column1', type='STRING', precision=null, scale=null,
> comment='null'}]
> {code}
> Debug from Hive view 1.5.0:
> {code:java}
> 27 Feb 2018 20:13:15,881 INFO [ambari-client-thread-38] [HIVE 1.5.0
> AUTO_HIVE_INSTANCE] UploadService:499 - isFirstRowHeader : true,
> inputFileType : CSV
> 27 Feb 2018 20:13:15,918 INFO [ambari-client-thread-38] [HIVE 1.5.0
> AUTO_HIVE_INSTANCE] OpenCSVParser:50 - setting delimiter as
> 27 Feb 2018 20:13:15,919 INFO [ambari-client-thread-38] [HIVE 1.5.0
> AUTO_HIVE_INSTANCE] OpenCSVParser:56 - setting Quote char : "
> 27 Feb 2018 20:13:15,919 INFO [ambari-client-thread-38] [HIVE 1.5.0
> AUTO_HIVE_INSTANCE] OpenCSVParser:62 - setting escapeChar : \
> 27 Feb 2018 20:13:15,928 INFO [ambari-client-thread-38] [HIVE 1.5.0
> AUTO_HIVE_INSTANCE] Parser:75 - generating preview for :
> ParseOptions{options={OPTIONS_CSV_QUOTE=", OPTIONS_CSV_DELIMITER= ,
> HEADER=FIRST_RECORD, FILE_TYPE=CSV, OPTIONS_CSV_ESCAPE_CHAR=\}}
> 27 Feb 2018 20:13:15,929 DEBUG [ambari-client-thread-38] [HIVE 1.5.0
> AUTO_HIVE_INSTANCE] Parser:83 - Illegal number of preview columns supplied
> null
> 27 Feb 2018 20:13:15,936 DEBUG [ambari-client-thread-38] [HIVE 1.5.0
> AUTO_HIVE_INSTANCE] ParseUtils:152 - error while parsing as timestamp string
> AD
> java.lang.IllegalArgumentException: Timestamp format must be -mm-dd
> hh:mm:ss[.f]
> at java.sql.Timest
[jira] [Assigned] (AMBARI-23179) Hive view 2.0 does not parse the TAB delimited CSV files while using 'Upload Table'
[
https://issues.apache.org/jira/browse/AMBARI-23179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nitiraj Singh Rathore reassigned AMBARI-23179:
--
Assignee: Nitiraj Singh Rathore
> Hive view 2.0 does not parse the TAB delimited CSV files while using 'Upload
> Table'
> ---
>
> Key: AMBARI-23179
> URL: https://issues.apache.org/jira/browse/AMBARI-23179
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.6.0
> Environment: HDP 2.6.3
> Ambari 2.6.0
>Reporter: Sindhu Subhas
>Assignee: Nitiraj Singh Rathore
>Priority: Major
> Attachments: Screen Shot 2018-02-28 at 1.02.44 AM.png, Screen Shot
> 2018-02-28 at 5.05.55 PM.png, Screen Shot 2018-02-28 at 5.06.47 PM.png,
> Screen Shot 2018-02-28 at 5.07.30 PM.png, datatab.tsv
>
>
> Problem:
> When trying to Upload table from Hive view 2.0 from a TAB delimited file, the
> data is not parsed as expected.
> Same feature works as expected in Hive view 1.5.0.
> Attached output from Hive view 2.0 and output from Hive view 1.5.0.
> From the code, we do see difference in the code for
> src/main/java/org/apache/ambari/view/hive20/resources/uploads/UploadService.java.
> Debug from Hive view 2.0:
> {code:java}
> 27 Feb 2018 20:27:28,169 DEBUG
> [HiveViewActorSystem-akka.actor.default-dispatcher-4] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] OperationController:53 - } java.util.HashMap
> 27 Feb 2018 20:27:28,169 DEBUG
> [HiveViewActorSystem-akka.actor.default-dispatcher-4] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] HiveActor:41 - Message submitted:
> 927343c0-5ed6-435c-be60-37448ac1a8b0
> 27 Feb 2018 20:27:30,925 INFO [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] UploadService:484 - isFirstRowHeader : false,
> inputFileType : CSV
> 27 Feb 2018 20:27:30,934 INFO [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] OpenCSVParser:50 - setting delimiter as T
> 27 Feb 2018 20:27:30,934 INFO [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] OpenCSVParser:56 - setting Quote char : "
> 27 Feb 2018 20:27:30,934 INFO [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] OpenCSVParser:62 - setting escapeChar : \
> 27 Feb 2018 20:27:30,939 INFO [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] Parser:75 - generating preview for :
> ParseOptions{options={OPTIONS_CSV_QUOTE=", OPTIONS_CSV_DELIMITER=T,
> HEADER=NONE, FILE_TYPE=CSV, OPTIONS_CSV_ESCAPE_CHAR=\}}
> 27 Feb 2018 20:27:30,939 DEBUG [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] Parser:83 - Illegal number of preview columns supplied
> null
> 27 Feb 2018 20:27:30,943 DEBUG [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] ParseUtils:152 - error while parsing as timestamp
> string column1 column2 column3
> java.lang.IllegalArgumentException: Timestamp format must be -mm-dd
> hh:mm:ss[.f]
> at java.sql.Timestamp.valueOf(Timestamp.java:204)
> .
> 27 Feb 2018 20:27:30,948 INFO [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] Parser:149 - datatype detected for column 0 : STRING
> 27 Feb 2018 20:27:30,949 DEBUG [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] Parser:159 - return headers :
> [ColumnInfo{name='column1', type='STRING', precision=null, scale=null,
> comment='null'}]
> {code}
> Debug from Hive view 1.5.0:
> {code:java}
> 27 Feb 2018 20:13:15,881 INFO [ambari-client-thread-38] [HIVE 1.5.0
> AUTO_HIVE_INSTANCE] UploadService:499 - isFirstRowHeader : true,
> inputFileType : CSV
> 27 Feb 2018 20:13:15,918 INFO [ambari-client-thread-38] [HIVE 1.5.0
> AUTO_HIVE_INSTANCE] OpenCSVParser:50 - setting delimiter as
> 27 Feb 2018 20:13:15,919 INFO [ambari-client-thread-38] [HIVE 1.5.0
> AUTO_HIVE_INSTANCE] OpenCSVParser:56 - setting Quote char : "
> 27 Feb 2018 20:13:15,919 INFO [ambari-client-thread-38] [HIVE 1.5.0
> AUTO_HIVE_INSTANCE] OpenCSVParser:62 - setting escapeChar : \
> 27 Feb 2018 20:13:15,928 INFO [ambari-client-thread-38] [HIVE 1.5.0
> AUTO_HIVE_INSTANCE] Parser:75 - generating preview for :
> ParseOptions{options={OPTIONS_CSV_QUOTE=", OPTIONS_CSV_DELIMITER= ,
> HEADER=FIRST_RECORD, FILE_TYPE=CSV, OPTIONS_CSV_ESCAPE_CHAR=\}}
> 27 Feb 2018 20:13:15,929 DEBUG [ambari-client-thread-38] [HIVE 1.5.0
> AUTO_HIVE_INSTANCE] Parser:83 - Illegal number of preview columns supplied
> null
> 27 Feb 2018 20:13:15,936 DEBUG [ambari-client-thread-38] [HIVE 1.5.0
> AUTO_HIVE_INSTANCE] ParseUtils:152 - error while parsing as timestamp string
> AD
> java.lang.IllegalArgumentException: Timestamp format must be -mm-dd
> hh:mm:ss[.f]
> at java.sql.Timestamp.valueOf(Timestamp.java:204)
> .
> 27 Feb 2018 20:13:15,961 INFO [ambari-client-threa
[jira] [Updated] (AMBARI-22999) Ambari Hive View 2.0 'Upload Table' does not support UTF8 files with BOM
[ https://issues.apache.org/jira/browse/AMBARI-22999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-22999: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Ambari Hive View 2.0 'Upload Table' does not support UTF8 files with BOM > > > Key: AMBARI-22999 > URL: https://issues.apache.org/jira/browse/AMBARI-22999 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Hajime Osako >Assignee: Nitiraj Singh Rathore >Priority: Major > Labels: pull-request-available > Fix For: 2.6.2 > > Time Spent: 1h > Remaining Estimate: 0h > > Creating this Jira to request same fix as AMBARI-18583 for Ambari Hive 2.0 > View. >  -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22999) Ambari Hive View 2.0 'Upload Table' does not support UTF8 files with BOM
[ https://issues.apache.org/jira/browse/AMBARI-22999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-22999: --- Fix Version/s: 2.6.2 Status: Patch Available (was: In Progress) > Ambari Hive View 2.0 'Upload Table' does not support UTF8 files with BOM > > > Key: AMBARI-22999 > URL: https://issues.apache.org/jira/browse/AMBARI-22999 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Hajime Osako >Assignee: Nitiraj Singh Rathore >Priority: Major > Labels: pull-request-available > Fix For: 2.6.2 > > Time Spent: 10m > Remaining Estimate: 0h > > Creating this Jira to request same fix as AMBARI-18583 for Ambari Hive 2.0 > View. >  -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-22999) Ambari Hive View 2.0 'Upload Table' does not support UTF8 files with BOM
[ https://issues.apache.org/jira/browse/AMBARI-22999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore reassigned AMBARI-22999: -- Assignee: Nitiraj Singh Rathore > Ambari Hive View 2.0 'Upload Table' does not support UTF8 files with BOM > > > Key: AMBARI-22999 > URL: https://issues.apache.org/jira/browse/AMBARI-22999 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Hajime Osako >Assignee: Nitiraj Singh Rathore >Priority: Major > > Creating this Jira to request same fix as AMBARI-18583 for Ambari Hive 2.0 > View. >  -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-22833) change commons-collections-3.2.1.jar being used by ambari views to commons-collections-3.2.2.jar
[ https://issues.apache.org/jira/browse/AMBARI-22833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore resolved AMBARI-22833. Resolution: Fixed Fix Version/s: 2.6.1 2.6.0 Pull request approved and merged. Above build failures in jenkins are in different modules not related to this changes. So closing the bug. > change commons-collections-3.2.1.jar being used by ambari views to > commons-collections-3.2.2.jar > > > Key: AMBARI-22833 > URL: https://issues.apache.org/jira/browse/AMBARI-22833 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore >Priority: Major > Labels: pull-request-available > Fix For: 2.5.3, 2.6.0, 2.6.1 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > This library should be replaced by newer version of commons-collection or > atleast 2.3.2, should be used. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22833) change commons-collections-3.2.1.jar being used by ambari views to commons-collections-3.2.2.jar
[ https://issues.apache.org/jira/browse/AMBARI-22833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-22833: --- Summary: change commons-collections-3.2.1.jar being used by ambari views to commons-collections-3.2.2.jar (was: java deserialization vulnerability for commons-collections-3.2.1.jar being used by ambari views.) > change commons-collections-3.2.1.jar being used by ambari views to > commons-collections-3.2.2.jar > > > Key: AMBARI-22833 > URL: https://issues.apache.org/jira/browse/AMBARI-22833 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore >Priority: Major > Fix For: 2.5.3 > > > This library should be replaced by newer version of commons-collection or > atleast 2.3.2, should be used. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-22833) java deserialization vulnerability for commons-collections-3.2.1.jar being used by ambari views.
Nitiraj Singh Rathore created AMBARI-22833: -- Summary: java deserialization vulnerability for commons-collections-3.2.1.jar being used by ambari views. Key: AMBARI-22833 URL: https://issues.apache.org/jira/browse/AMBARI-22833 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Nitiraj Singh Rathore Assignee: Nitiraj Singh Rathore Fix For: 2.5.3 This library should be replaced by newer version of commons-collection or atleast 2.3.2, should be used. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22202) Hive View 2.0 in Ambari 2.5.1 does not use the specified YARN queue when using the "Upload Table" feature.
[ https://issues.apache.org/jira/browse/AMBARI-22202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-22202: --- Resolution: Fixed Status: Resolved (was: Patch Available) committed to branch-2.6 and trunk > Hive View 2.0 in Ambari 2.5.1 does not use the specified YARN queue when > using the "Upload Table" feature. > -- > > Key: AMBARI-22202 > URL: https://issues.apache.org/jira/browse/AMBARI-22202 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.6.0 > > Attachments: AMBARI-22202_branch-2.6.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22202) Hive View 2.0 in Ambari 2.5.1 does not use the specified YARN queue when using the "Upload Table" feature.
[ https://issues.apache.org/jira/browse/AMBARI-22202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-22202: --- Status: Patch Available (was: Open) > Hive View 2.0 in Ambari 2.5.1 does not use the specified YARN queue when > using the "Upload Table" feature. > -- > > Key: AMBARI-22202 > URL: https://issues.apache.org/jira/browse/AMBARI-22202 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.6.0 > > Attachments: AMBARI-22202_branch-2.6.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22202) Hive View 2.0 in Ambari 2.5.1 does not use the specified YARN queue when using the "Upload Table" feature.
[ https://issues.apache.org/jira/browse/AMBARI-22202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-22202: --- Attachment: AMBARI-22202_branch-2.6.patch > Hive View 2.0 in Ambari 2.5.1 does not use the specified YARN queue when > using the "Upload Table" feature. > -- > > Key: AMBARI-22202 > URL: https://issues.apache.org/jira/browse/AMBARI-22202 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.6.0 > > Attachments: AMBARI-22202_branch-2.6.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22202) Hive View 2.0 in Ambari 2.5.1 does not use the specified YARN queue when using the "Upload Table" feature.
Nitiraj Singh Rathore created AMBARI-22202: -- Summary: Hive View 2.0 in Ambari 2.5.1 does not use the specified YARN queue when using the "Upload Table" feature. Key: AMBARI-22202 URL: https://issues.apache.org/jira/browse/AMBARI-22202 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Nitiraj Singh Rathore Assignee: Nitiraj Singh Rathore Fix For: 2.6.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21799) Hive query failing randomly with Null point exception status 500
[
https://issues.apache.org/jira/browse/AMBARI-21799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nitiraj Singh Rathore updated AMBARI-21799:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
committed to branch-2.6 and trunk
> Hive query failing randomly with Null point exception status 500
>
>
> Key: AMBARI-21799
> URL: https://issues.apache.org/jira/browse/AMBARI-21799
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.1
>Reporter: amarnath reddy pappu
>Assignee: Nitiraj Singh Rathore
> Fix For: 2.6.0
>
> Attachments: AMBARI-21799_branch-2.6.patch
>
>
> Hive query failing randomly with below error.
> Status: 500
> Message:
> full stack trace
> Code snippet that is causing the issue is:
> In HdfsApi.java
> tryNumber += 1;
> try
> { result = ugi.doAs(action); succeeded = true; }
> catch (IOException ex) {
> if (!ex.getMessage().contains("Cannot obtain block length for"))
> { throw ex; }
> HDFS is returning the exception without message and it kept failing at that
> point.
> E090 NullPointerException
> Trace:
> java.lang.NullPointerException
> java.lang.NullPointerException
> at org.apache.ambari.view.utils.hdfs.HdfsApi.execute(HdfsApi.java:404)
> at org.apache.ambari.view.utils.hdfs.HdfsApi.create(HdfsApi.java:310)
> at
> org.apache.ambari.view.utils.hdfs.HdfsUtil.putStringToFile(HdfsUtil.java:45)
> at
> org.apache.ambari.view.hive20.resources.jobs.viewJobs.JobControllerImpl.setupQueryFile(JobControllerImpl.java:267)
>
> at
> org.apache.ambari.view.hive20.resources.jobs.viewJobs.JobControllerImpl.setupQueryFileIfNotPresent(JobControllerImpl.java:195)
>
> at
> org.apache.ambari.view.hive20.resources.jobs.viewJobs.JobControllerImpl.afterCreation(JobControllerImpl.java:181)
>
> at
> org.apache.ambari.view.hive20.resources.jobs.viewJobs.JobResourceManager.create(JobResourceManager.java:56)
>
> at
> org.apache.ambari.view.hive20.resources.jobs.JobServiceInternal.createJob(JobServiceInternal.java:27)
>
> at
> org.apache.ambari.view.hive20.resources.jobs.JobService.create(JobService.java:500)
>
> at sun.reflect.GeneratedMethodAccessor1412.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
>
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
>
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
>
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
>
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
>
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
>
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
>
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
>
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
>
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
>
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
>
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
>
> at
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
>
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
>
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
>
> at javax.servlet.http.HttpServlet.se
[jira] [Updated] (AMBARI-21799) Hive query failing randomly with Null point exception status 500
[
https://issues.apache.org/jira/browse/AMBARI-21799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nitiraj Singh Rathore updated AMBARI-21799:
---
Assignee: Nitiraj Singh Rathore
Status: Patch Available (was: Open)
> Hive query failing randomly with Null point exception status 500
>
>
> Key: AMBARI-21799
> URL: https://issues.apache.org/jira/browse/AMBARI-21799
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.1
>Reporter: amarnath reddy pappu
>Assignee: Nitiraj Singh Rathore
> Fix For: 2.6.0
>
> Attachments: AMBARI-21799_branch-2.6.patch
>
>
> Hive query failing randomly with below error.
> Status: 500
> Message:
> full stack trace
> Code snippet that is causing the issue is:
> In HdfsApi.java
> tryNumber += 1;
> try
> { result = ugi.doAs(action); succeeded = true; }
> catch (IOException ex) {
> if (!ex.getMessage().contains("Cannot obtain block length for"))
> { throw ex; }
> HDFS is returning the exception without message and it kept failing at that
> point.
> E090 NullPointerException
> Trace:
> java.lang.NullPointerException
> java.lang.NullPointerException
> at org.apache.ambari.view.utils.hdfs.HdfsApi.execute(HdfsApi.java:404)
> at org.apache.ambari.view.utils.hdfs.HdfsApi.create(HdfsApi.java:310)
> at
> org.apache.ambari.view.utils.hdfs.HdfsUtil.putStringToFile(HdfsUtil.java:45)
> at
> org.apache.ambari.view.hive20.resources.jobs.viewJobs.JobControllerImpl.setupQueryFile(JobControllerImpl.java:267)
>
> at
> org.apache.ambari.view.hive20.resources.jobs.viewJobs.JobControllerImpl.setupQueryFileIfNotPresent(JobControllerImpl.java:195)
>
> at
> org.apache.ambari.view.hive20.resources.jobs.viewJobs.JobControllerImpl.afterCreation(JobControllerImpl.java:181)
>
> at
> org.apache.ambari.view.hive20.resources.jobs.viewJobs.JobResourceManager.create(JobResourceManager.java:56)
>
> at
> org.apache.ambari.view.hive20.resources.jobs.JobServiceInternal.createJob(JobServiceInternal.java:27)
>
> at
> org.apache.ambari.view.hive20.resources.jobs.JobService.create(JobService.java:500)
>
> at sun.reflect.GeneratedMethodAccessor1412.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
>
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
>
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
>
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
>
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
>
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
>
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
>
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
>
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
>
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
>
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
>
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
>
> at
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
>
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
>
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
>
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
[jira] [Updated] (AMBARI-21799) Hive query failing randomly with Null point exception status 500
[
https://issues.apache.org/jira/browse/AMBARI-21799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nitiraj Singh Rathore updated AMBARI-21799:
---
Attachment: AMBARI-21799_branch-2.6.patch
> Hive query failing randomly with Null point exception status 500
>
>
> Key: AMBARI-21799
> URL: https://issues.apache.org/jira/browse/AMBARI-21799
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.1
>Reporter: amarnath reddy pappu
> Fix For: 2.6.0
>
> Attachments: AMBARI-21799_branch-2.6.patch
>
>
> Hive query failing randomly with below error.
> Status: 500
> Message:
> full stack trace
> Code snippet that is causing the issue is:
> In HdfsApi.java
> tryNumber += 1;
> try
> { result = ugi.doAs(action); succeeded = true; }
> catch (IOException ex) {
> if (!ex.getMessage().contains("Cannot obtain block length for"))
> { throw ex; }
> HDFS is returning the exception without message and it kept failing at that
> point.
> E090 NullPointerException
> Trace:
> java.lang.NullPointerException
> java.lang.NullPointerException
> at org.apache.ambari.view.utils.hdfs.HdfsApi.execute(HdfsApi.java:404)
> at org.apache.ambari.view.utils.hdfs.HdfsApi.create(HdfsApi.java:310)
> at
> org.apache.ambari.view.utils.hdfs.HdfsUtil.putStringToFile(HdfsUtil.java:45)
> at
> org.apache.ambari.view.hive20.resources.jobs.viewJobs.JobControllerImpl.setupQueryFile(JobControllerImpl.java:267)
>
> at
> org.apache.ambari.view.hive20.resources.jobs.viewJobs.JobControllerImpl.setupQueryFileIfNotPresent(JobControllerImpl.java:195)
>
> at
> org.apache.ambari.view.hive20.resources.jobs.viewJobs.JobControllerImpl.afterCreation(JobControllerImpl.java:181)
>
> at
> org.apache.ambari.view.hive20.resources.jobs.viewJobs.JobResourceManager.create(JobResourceManager.java:56)
>
> at
> org.apache.ambari.view.hive20.resources.jobs.JobServiceInternal.createJob(JobServiceInternal.java:27)
>
> at
> org.apache.ambari.view.hive20.resources.jobs.JobService.create(JobService.java:500)
>
> at sun.reflect.GeneratedMethodAccessor1412.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
>
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
>
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
>
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
>
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
>
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
>
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
>
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
>
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
>
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
>
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
>
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
>
> at
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
>
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
>
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
>
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
[jira] [Updated] (AMBARI-21108) Unable to upload table via Ambari Hive view if user does not have permission on default database
[ https://issues.apache.org/jira/browse/AMBARI-21108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-21108: --- Resolution: Fixed Status: Resolved (was: Patch Available) committed to branch-2.5 and trunk. > Unable to upload table via Ambari Hive view if user does not have permission > on default database > > > Key: AMBARI-21108 > URL: https://issues.apache.org/jira/browse/AMBARI-21108 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.2 > > Attachments: AMBARI-21108_branch-2.5.patch > > > Hive View : upload table code runs queries against 'default' database. which > requires users to have permission on this database even though table is being > uploaded in another database. > Its a bug in hive view 1.5. > This bug is also present in hive view 1.5 of ambari release 2.5. > It will not occur in hive view 2.0 which is release with ambari 2.5. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-20929) Changes in Zeppelin JDBC config after ZEPPELIN-2367
[ https://issues.apache.org/jira/browse/AMBARI-20929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-20929: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Changes in Zeppelin JDBC config after ZEPPELIN-2367 > --- > > Key: AMBARI-20929 > URL: https://issues.apache.org/jira/browse/AMBARI-20929 > Project: Ambari > Issue Type: Bug >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Attachments: AMBARI-20929_trunk_v1.patch > > > After ZEPPELIN-2367 there are configuration parameter changes that required > to make user impersonation for JDBC interpreter. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20929) Changes in Zeppelin JDBC config after ZEPPELIN-2367
[ https://issues.apache.org/jira/browse/AMBARI-20929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16044165#comment-16044165 ] Nitiraj Singh Rathore commented on AMBARI-20929: committed to branch-2.5 and trunk > Changes in Zeppelin JDBC config after ZEPPELIN-2367 > --- > > Key: AMBARI-20929 > URL: https://issues.apache.org/jira/browse/AMBARI-20929 > Project: Ambari > Issue Type: Bug >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Attachments: AMBARI-20929_trunk_v1.patch > > > After ZEPPELIN-2367 there are configuration parameter changes that required > to make user impersonation for JDBC interpreter. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21174) File View : Download using Concatenate results in incorrect data
[ https://issues.apache.org/jira/browse/AMBARI-21174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-21174: --- Resolution: Fixed Status: Resolved (was: Patch Available) file was getting incorrectly copied from input stream to output stream. committed to trunk and branch-2.5 > File View : Download using Concatenate results in incorrect data > > > Key: AMBARI-21174 > URL: https://issues.apache.org/jira/browse/AMBARI-21174 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.2 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.2 > > Attachments: AMBARI-21174_branch-2.5.patch > > > In Ambari File Views, when we use the concatenate button to concatenate two > or more files, the downloaded file has more data (rows) in it than the > original records. > STEPS TO REPRODUCE: > Step 1: Go to Ambari File Views > Step2: Select atleast 2 files and click on "Concatentate" button. > Step3: Open the downloaded file and review the line count. > EXPECTED RESULT: > The number of rows in the downloaded file should exactly be the sum of the > number of lines from the selected files. > ACTUAL RESULT: The lines in the downloaded file is more. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21163) Hive view not exporting/downloading the worksheet with entire number of rows to csv
[ https://issues.apache.org/jira/browse/AMBARI-21163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-21163: --- Resolution: Fixed Status: Resolved (was: Patch Available) committed to branch-2.5 and trunk > Hive view not exporting/downloading the worksheet with entire number of rows > to csv > --- > > Key: AMBARI-21163 > URL: https://issues.apache.org/jira/browse/AMBARI-21163 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Tauseef Hussain >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.2 > > Attachments: AMBARI-21163_branch-2.5.patch > > > When running a query in Hive view which returns a large number of records > (~million rows) and then subsequently trying to download this result to CSV > file, the download always shows as having completed successfully but never > downloads the entire result set. > The behavior is consistent across both Hive 1.5 and Hive 2.0 views -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21174) File View : Download using Concatenate results in incorrect data
[ https://issues.apache.org/jira/browse/AMBARI-21174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-21174: --- Status: Patch Available (was: Open) > File View : Download using Concatenate results in incorrect data > > > Key: AMBARI-21174 > URL: https://issues.apache.org/jira/browse/AMBARI-21174 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.2 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.2 > > Attachments: AMBARI-21174_branch-2.5.patch > > > In Ambari File Views, when we use the concatenate button to concatenate two > or more files, the downloaded file has more data (rows) in it than the > original records. > STEPS TO REPRODUCE: > Step 1: Go to Ambari File Views > Step2: Select atleast 2 files and click on "Concatentate" button. > Step3: Open the downloaded file and review the line count. > EXPECTED RESULT: > The number of rows in the downloaded file should exactly be the sum of the > number of lines from the selected files. > ACTUAL RESULT: The lines in the downloaded file is more. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21174) File View : Download using Concatenate results in incorrect data
[ https://issues.apache.org/jira/browse/AMBARI-21174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-21174: --- Attachment: AMBARI-21174_branch-2.5.patch > File View : Download using Concatenate results in incorrect data > > > Key: AMBARI-21174 > URL: https://issues.apache.org/jira/browse/AMBARI-21174 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.2 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.2 > > Attachments: AMBARI-21174_branch-2.5.patch > > > In Ambari File Views, when we use the concatenate button to concatenate two > or more files, the downloaded file has more data (rows) in it than the > original records. > STEPS TO REPRODUCE: > Step 1: Go to Ambari File Views > Step2: Select atleast 2 files and click on "Concatentate" button. > Step3: Open the downloaded file and review the line count. > EXPECTED RESULT: > The number of rows in the downloaded file should exactly be the sum of the > number of lines from the selected files. > ACTUAL RESULT: The lines in the downloaded file is more. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21174) File View : Download using Concatenate results in incorrect data
[ https://issues.apache.org/jira/browse/AMBARI-21174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-21174: --- Affects Version/s: (was: 2.5.0) 2.4.2 > File View : Download using Concatenate results in incorrect data > > > Key: AMBARI-21174 > URL: https://issues.apache.org/jira/browse/AMBARI-21174 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.2 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.2 > > > In Ambari File Views, when we use the concatenate button to concatenate two > or more files, the downloaded file has more data (rows) in it than the > original records. > STEPS TO REPRODUCE: > Step 1: Go to Ambari File Views > Step2: Select atleast 2 files and click on "Concatentate" button. > Step3: Open the downloaded file and review the line count. > EXPECTED RESULT: > The number of rows in the downloaded file should exactly be the sum of the > number of lines from the selected files. > ACTUAL RESULT: The lines in the downloaded file is more. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-21174) File View : Download using Concatenate results in incorrect data
Nitiraj Singh Rathore created AMBARI-21174: -- Summary: File View : Download using Concatenate results in incorrect data Key: AMBARI-21174 URL: https://issues.apache.org/jira/browse/AMBARI-21174 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Nitiraj Singh Rathore Assignee: Nitiraj Singh Rathore Fix For: 2.5.2 In Ambari File Views, when we use the concatenate button to concatenate two or more files, the downloaded file has more data (rows) in it than the original records. STEPS TO REPRODUCE: Step 1: Go to Ambari File Views Step2: Select atleast 2 files and click on "Concatentate" button. Step3: Open the downloaded file and review the line count. EXPECTED RESULT: The number of rows in the downloaded file should exactly be the sum of the number of lines from the selected files. ACTUAL RESULT: The lines in the downloaded file is more. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21163) Hive view not exporting/downloading the worksheet with entire number of rows to csv
[ https://issues.apache.org/jira/browse/AMBARI-21163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-21163: --- Assignee: Nitiraj Singh Rathore Status: Patch Available (was: Open) > Hive view not exporting/downloading the worksheet with entire number of rows > to csv > --- > > Key: AMBARI-21163 > URL: https://issues.apache.org/jira/browse/AMBARI-21163 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Tauseef Hussain >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.2 > > Attachments: AMBARI-21163_branch-2.5.patch > > > When running a query in Hive view which returns a large number of records > (~million rows) and then subsequently trying to download this result to CSV > file, the download always shows as having completed successfully but never > downloads the entire result set. > The behavior is consistent across both Hive 1.5 and Hive 2.0 views -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21163) Hive view not exporting/downloading the worksheet with entire number of rows to csv
[ https://issues.apache.org/jira/browse/AMBARI-21163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-21163: --- Attachment: AMBARI-21163_branch-2.5.patch > Hive view not exporting/downloading the worksheet with entire number of rows > to csv > --- > > Key: AMBARI-21163 > URL: https://issues.apache.org/jira/browse/AMBARI-21163 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Tauseef Hussain > Fix For: 2.5.2 > > Attachments: AMBARI-21163_branch-2.5.patch > > > When running a query in Hive view which returns a large number of records > (~million rows) and then subsequently trying to download this result to CSV > file, the download always shows as having completed successfully but never > downloads the entire result set. > The behavior is consistent across both Hive 1.5 and Hive 2.0 views -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21163) Hive view not exporting/downloading the worksheet with entire number of rows to csv
[ https://issues.apache.org/jira/browse/AMBARI-21163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-21163: --- Fix Version/s: 2.5.2 > Hive view not exporting/downloading the worksheet with entire number of rows > to csv > --- > > Key: AMBARI-21163 > URL: https://issues.apache.org/jira/browse/AMBARI-21163 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Tauseef Hussain > Fix For: 2.5.2 > > > When running a query in Hive view which returns a large number of records > (~million rows) and then subsequently trying to download this result to CSV > file, the download always shows as having completed successfully but never > downloads the entire result set. > The behavior is consistent across both Hive 1.5 and Hive 2.0 views -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21108) Unable to upload table via Ambari Hive view if user does not have permission on default database
[ https://issues.apache.org/jira/browse/AMBARI-21108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-21108: --- Status: Patch Available (was: Open) > Unable to upload table via Ambari Hive view if user does not have permission > on default database > > > Key: AMBARI-21108 > URL: https://issues.apache.org/jira/browse/AMBARI-21108 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.2 > > Attachments: AMBARI-21108_branch-2.5.patch > > > Hive View : upload table code runs queries against 'default' database. which > requires users to have permission on this database even though table is being > uploaded in another database. > Its a bug in hive view 1.5. > This bug is also present in hive view 1.5 of ambari release 2.5. > It will not occur in hive view 2.0 which is release with ambari 2.5. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21108) Unable to upload table via Ambari Hive view if user does not have permission on default database
[ https://issues.apache.org/jira/browse/AMBARI-21108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-21108: --- Attachment: AMBARI-21108_branch-2.5.patch Hive view 1.5 was using default DB for use statement in upload table feature. corrected it to use selected database > Unable to upload table via Ambari Hive view if user does not have permission > on default database > > > Key: AMBARI-21108 > URL: https://issues.apache.org/jira/browse/AMBARI-21108 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.2 > > Attachments: AMBARI-21108_branch-2.5.patch > > > Hive View : upload table code runs queries against 'default' database. which > requires users to have permission on this database even though table is being > uploaded in another database. > Its a bug in hive view 1.5. > This bug is also present in hive view 1.5 of ambari release 2.5. > It will not occur in hive view 2.0 which is release with ambari 2.5. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-21108) Unable to upload table via Ambari Hive view if user does not have permission on default database
Nitiraj Singh Rathore created AMBARI-21108: -- Summary: Unable to upload table via Ambari Hive view if user does not have permission on default database Key: AMBARI-21108 URL: https://issues.apache.org/jira/browse/AMBARI-21108 Project: Ambari Issue Type: Bug Affects Versions: 2.4.0 Reporter: Nitiraj Singh Rathore Assignee: Nitiraj Singh Rathore Fix For: 2.5.2 Hive View : upload table code runs queries against 'default' database. which requires users to have permission on this database even though table is being uploaded in another database. Its a bug in hive view 1.5. This bug is also present in hive view 1.5 of ambari release 2.5. It will not occur in hive view 2.0 which is release with ambari 2.5. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20990) Hive view 1.5 : Saved query garbles the unicode characters in query.
[ https://issues.apache.org/jira/browse/AMBARI-20990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-20990: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > Hive view 1.5 : Saved query garbles the unicode characters in query. > > > Key: AMBARI-20990 > URL: https://issues.apache.org/jira/browse/AMBARI-20990 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.2 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.1 > > Attachments: AMBARI-20990_branch-2.5.patch > > > Steps to reproduce. > 1. Open query editor of hive view 1.5. > 2. Enter a simple query with unicode character like > select '昔々' > 3. click on "save as" button. Save the query. > 4. Refresh page. Go to the saved queries tab and click open the saved query. > 5. in the query editor you will not see the unicode characters you entered. > Instead you will see some garbled characters. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20981) Hive 2.0 View Table Statistics overflows Integer Type convert to Long
[ https://issues.apache.org/jira/browse/AMBARI-20981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16007578#comment-16007578 ] Nitiraj Singh Rathore commented on AMBARI-20981: committed to branch-2.5 and trunk. > Hive 2.0 View Table Statistics overflows Integer Type convert to Long > - > > Key: AMBARI-20981 > URL: https://issues.apache.org/jira/browse/AMBARI-20981 > Project: Ambari > Issue Type: Bug > Components: contrib >Affects Versions: 2.5.0, 2.5.1, 2.5.2 > Environment: Ambari 2.5.0.x >Reporter: Greg Senia > Labels: views > Attachments: AMBARI-20981_branch-2.5.patch, AMBARI-20981.patch > > > When testing with our extremely large datasets the statistics data returns a > failure and the following stack trace. Using Integer for Hive Table Stats > unfortunately is not going to work. It needs to be a long. I've provided a > patch to fix this. > 09 May 2017 10:24:34,474 ERROR [ambari-client-thread-55044] > ContainerResponse:419 - The RuntimeException could not be mapped to a > response, re-throwing to the HT > TP container > java.lang.NumberFormatException: For input string: "12375183159" > at > java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) > at java.lang.Integer.parseInt(Integer.java:583) > at java.lang.Integer.valueOf(Integer.java:766) > at > org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.getTableStats(TableMetaParserImpl.java:115) > at > org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.parse(TableMetaParserImpl.java:62) > at > org.apache.ambari.view.hive20.resources.browser.DDLProxy.getTableProperties(DDLProxy.java:157) > at > org.apache.ambari.view.hive20.resources.browser.DDLService.getTableInfo(DDLService.java:278) > at sun.reflect.GeneratedMethodAccessor253.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > at > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84) > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542) > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473) > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419) > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409) > at > com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) > at > org.eclipse.jetty.servlet.ServletHo
[jira] [Updated] (AMBARI-20981) Hive 2.0 View Table Statistics overflows Integer Type convert to Long
[ https://issues.apache.org/jira/browse/AMBARI-20981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-20981: --- Resolution: Fixed Assignee: Nitiraj Singh Rathore Fix Version/s: 2.5.1 Status: Resolved (was: Patch Available) > Hive 2.0 View Table Statistics overflows Integer Type convert to Long > - > > Key: AMBARI-20981 > URL: https://issues.apache.org/jira/browse/AMBARI-20981 > Project: Ambari > Issue Type: Bug > Components: contrib >Affects Versions: 2.5.0 > Environment: Ambari 2.5.0.x >Reporter: Greg Senia >Assignee: Nitiraj Singh Rathore > Labels: views > Fix For: 2.5.1 > > Attachments: AMBARI-20981_branch-2.5.patch, AMBARI-20981.patch > > > When testing with our extremely large datasets the statistics data returns a > failure and the following stack trace. Using Integer for Hive Table Stats > unfortunately is not going to work. It needs to be a long. I've provided a > patch to fix this. > 09 May 2017 10:24:34,474 ERROR [ambari-client-thread-55044] > ContainerResponse:419 - The RuntimeException could not be mapped to a > response, re-throwing to the HT > TP container > java.lang.NumberFormatException: For input string: "12375183159" > at > java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) > at java.lang.Integer.parseInt(Integer.java:583) > at java.lang.Integer.valueOf(Integer.java:766) > at > org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.getTableStats(TableMetaParserImpl.java:115) > at > org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.parse(TableMetaParserImpl.java:62) > at > org.apache.ambari.view.hive20.resources.browser.DDLProxy.getTableProperties(DDLProxy.java:157) > at > org.apache.ambari.view.hive20.resources.browser.DDLService.getTableInfo(DDLService.java:278) > at sun.reflect.GeneratedMethodAccessor253.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > at > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84) > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542) > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473) > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419) > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409) > at > com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733) > at
[jira] [Updated] (AMBARI-20981) Hive 2.0 View Table Statistics overflows Integer Type convert to Long
[ https://issues.apache.org/jira/browse/AMBARI-20981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-20981: --- Affects Version/s: (was: 2.5.2) (was: 2.5.1) > Hive 2.0 View Table Statistics overflows Integer Type convert to Long > - > > Key: AMBARI-20981 > URL: https://issues.apache.org/jira/browse/AMBARI-20981 > Project: Ambari > Issue Type: Bug > Components: contrib >Affects Versions: 2.5.0 > Environment: Ambari 2.5.0.x >Reporter: Greg Senia >Assignee: Nitiraj Singh Rathore > Labels: views > Fix For: 2.5.1 > > Attachments: AMBARI-20981_branch-2.5.patch, AMBARI-20981.patch > > > When testing with our extremely large datasets the statistics data returns a > failure and the following stack trace. Using Integer for Hive Table Stats > unfortunately is not going to work. It needs to be a long. I've provided a > patch to fix this. > 09 May 2017 10:24:34,474 ERROR [ambari-client-thread-55044] > ContainerResponse:419 - The RuntimeException could not be mapped to a > response, re-throwing to the HT > TP container > java.lang.NumberFormatException: For input string: "12375183159" > at > java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) > at java.lang.Integer.parseInt(Integer.java:583) > at java.lang.Integer.valueOf(Integer.java:766) > at > org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.getTableStats(TableMetaParserImpl.java:115) > at > org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.parse(TableMetaParserImpl.java:62) > at > org.apache.ambari.view.hive20.resources.browser.DDLProxy.getTableProperties(DDLProxy.java:157) > at > org.apache.ambari.view.hive20.resources.browser.DDLService.getTableInfo(DDLService.java:278) > at sun.reflect.GeneratedMethodAccessor253.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > at > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84) > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542) > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473) > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419) > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409) > at > com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) >
[jira] [Updated] (AMBARI-20990) Hive view 1.5 : Saved query garbles the unicode characters in query.
[ https://issues.apache.org/jira/browse/AMBARI-20990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-20990: --- Status: Patch Available (was: Open) > Hive view 1.5 : Saved query garbles the unicode characters in query. > > > Key: AMBARI-20990 > URL: https://issues.apache.org/jira/browse/AMBARI-20990 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.2 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.1 > > Attachments: AMBARI-20990_branch-2.5.patch > > > Steps to reproduce. > 1. Open query editor of hive view 1.5. > 2. Enter a simple query with unicode character like > select '昔々' > 3. click on "save as" button. Save the query. > 4. Refresh page. Go to the saved queries tab and click open the saved query. > 5. in the query editor you will not see the unicode characters you entered. > Instead you will see some garbled characters. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20990) Hive view 1.5 : Saved query garbles the unicode characters in query.
[ https://issues.apache.org/jira/browse/AMBARI-20990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-20990: --- Attachment: AMBARI-20990_branch-2.5.patch > Hive view 1.5 : Saved query garbles the unicode characters in query. > > > Key: AMBARI-20990 > URL: https://issues.apache.org/jira/browse/AMBARI-20990 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.2 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.1 > > Attachments: AMBARI-20990_branch-2.5.patch > > > Steps to reproduce. > 1. Open query editor of hive view 1.5. > 2. Enter a simple query with unicode character like > select '昔々' > 3. click on "save as" button. Save the query. > 4. Refresh page. Go to the saved queries tab and click open the saved query. > 5. in the query editor you will not see the unicode characters you entered. > Instead you will see some garbled characters. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20990) Hive view 1.5 : Saved query garbles the unicode characters in query.
[ https://issues.apache.org/jira/browse/AMBARI-20990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-20990: --- Description: Steps to reproduce. 1. Open query editor of hive view 1.5. 2. Enter a simple query with unicode character like > select '昔々' 3. click on "save as" button. Save the query. 4. Refresh page. Go to the saved queries tab and click open the saved query. 5. in the query editor you will not see the unicode characters you entered. Instead you will see some garbled characters. was: Steps to reproduce. 1. Open query editor of hive view 1.5. 2. Enter a simple query with unicode character like > select '昔々' 3. click on "save as" button. Save the query. 4. Go to the saved queries tab and click open the saved query. 5. in the query editor you will not see the unicode characters you entered. Instead you will see some garbled characters. > Hive view 1.5 : Saved query garbles the unicode characters in query. > > > Key: AMBARI-20990 > URL: https://issues.apache.org/jira/browse/AMBARI-20990 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.2 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.1 > > > Steps to reproduce. > 1. Open query editor of hive view 1.5. > 2. Enter a simple query with unicode character like > select '昔々' > 3. click on "save as" button. Save the query. > 4. Refresh page. Go to the saved queries tab and click open the saved query. > 5. in the query editor you will not see the unicode characters you entered. > Instead you will see some garbled characters. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20990) Hive view 1.5 : Saved query garbles the unicode characters in query.
Nitiraj Singh Rathore created AMBARI-20990: -- Summary: Hive view 1.5 : Saved query garbles the unicode characters in query. Key: AMBARI-20990 URL: https://issues.apache.org/jira/browse/AMBARI-20990 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.4.2 Reporter: Nitiraj Singh Rathore Assignee: Nitiraj Singh Rathore Fix For: 2.5.1 Steps to reproduce. 1. Open query editor of hive view 1.5. 2. Enter a simple query with unicode character like > select '昔々' 3. click on "save as" button. Save the query. 4. Go to the saved queries tab and click open the saved query. 5. in the query editor you will not see the unicode characters you entered. Instead you will see some garbled characters. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (AMBARI-20981) Hive 2.0 View Table Statistics overflows Integer Type convert to Long
[ https://issues.apache.org/jira/browse/AMBARI-20981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16006073#comment-16006073 ] Nitiraj Singh Rathore edited comment on AMBARI-20981 at 5/11/17 8:31 AM: - [~gss2002] : Thanks for the patch. Although, your patch seems to be made by git only, but I was having problems in applying to the branch. So I did the same changes and created a new patch. attached AMBARI-20981_branch-2.5.patch : new patch with formatting and message. was (Author: nitiraj.rathore): attached AMBARI-20981_branch-2.5.patch : new patch with formatting and message. > Hive 2.0 View Table Statistics overflows Integer Type convert to Long > - > > Key: AMBARI-20981 > URL: https://issues.apache.org/jira/browse/AMBARI-20981 > Project: Ambari > Issue Type: Bug > Components: contrib >Affects Versions: 2.5.0, 2.5.1, 2.5.2 > Environment: Ambari 2.5.0.x >Reporter: Greg Senia > Labels: views > Attachments: AMBARI-20981_branch-2.5.patch, AMBARI-20981.patch > > > When testing with our extremely large datasets the statistics data returns a > failure and the following stack trace. Using Integer for Hive Table Stats > unfortunately is not going to work. It needs to be a long. I've provided a > patch to fix this. > 09 May 2017 10:24:34,474 ERROR [ambari-client-thread-55044] > ContainerResponse:419 - The RuntimeException could not be mapped to a > response, re-throwing to the HT > TP container > java.lang.NumberFormatException: For input string: "12375183159" > at > java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) > at java.lang.Integer.parseInt(Integer.java:583) > at java.lang.Integer.valueOf(Integer.java:766) > at > org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.getTableStats(TableMetaParserImpl.java:115) > at > org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.parse(TableMetaParserImpl.java:62) > at > org.apache.ambari.view.hive20.resources.browser.DDLProxy.getTableProperties(DDLProxy.java:157) > at > org.apache.ambari.view.hive20.resources.browser.DDLService.getTableInfo(DDLService.java:278) > at sun.reflect.GeneratedMethodAccessor253.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > at > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84) > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542) > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473) > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419) > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409) > at > com.sun.jersey
[jira] [Comment Edited] (AMBARI-20981) Hive 2.0 View Table Statistics overflows Integer Type convert to Long
[ https://issues.apache.org/jira/browse/AMBARI-20981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16006073#comment-16006073 ] Nitiraj Singh Rathore edited comment on AMBARI-20981 at 5/11/17 8:25 AM: - attached AMBARI-20981_branch-2.5.patch : new patch with formatting and message. was (Author: nitiraj.rathore): attached AMBARI-20962_branch-2.5.patch : new patch with formatting and message. > Hive 2.0 View Table Statistics overflows Integer Type convert to Long > - > > Key: AMBARI-20981 > URL: https://issues.apache.org/jira/browse/AMBARI-20981 > Project: Ambari > Issue Type: Bug > Components: contrib >Affects Versions: 2.5.0, 2.5.1, 2.5.2 > Environment: Ambari 2.5.0.x >Reporter: Greg Senia > Labels: views > Attachments: AMBARI-20981_branch-2.5.patch, AMBARI-20981.patch > > > When testing with our extremely large datasets the statistics data returns a > failure and the following stack trace. Using Integer for Hive Table Stats > unfortunately is not going to work. It needs to be a long. I've provided a > patch to fix this. > 09 May 2017 10:24:34,474 ERROR [ambari-client-thread-55044] > ContainerResponse:419 - The RuntimeException could not be mapped to a > response, re-throwing to the HT > TP container > java.lang.NumberFormatException: For input string: "12375183159" > at > java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) > at java.lang.Integer.parseInt(Integer.java:583) > at java.lang.Integer.valueOf(Integer.java:766) > at > org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.getTableStats(TableMetaParserImpl.java:115) > at > org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.parse(TableMetaParserImpl.java:62) > at > org.apache.ambari.view.hive20.resources.browser.DDLProxy.getTableProperties(DDLProxy.java:157) > at > org.apache.ambari.view.hive20.resources.browser.DDLService.getTableInfo(DDLService.java:278) > at sun.reflect.GeneratedMethodAccessor253.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > at > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84) > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542) > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473) > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419) > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409) > at > com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558) > at > com.s
[jira] [Updated] (AMBARI-20981) Hive 2.0 View Table Statistics overflows Integer Type convert to Long
[ https://issues.apache.org/jira/browse/AMBARI-20981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-20981: --- Attachment: AMBARI-20981_branch-2.5.patch > Hive 2.0 View Table Statistics overflows Integer Type convert to Long > - > > Key: AMBARI-20981 > URL: https://issues.apache.org/jira/browse/AMBARI-20981 > Project: Ambari > Issue Type: Bug > Components: contrib >Affects Versions: 2.5.0, 2.5.1, 2.5.2 > Environment: Ambari 2.5.0.x >Reporter: Greg Senia > Labels: views > Attachments: AMBARI-20981_branch-2.5.patch, AMBARI-20981.patch > > > When testing with our extremely large datasets the statistics data returns a > failure and the following stack trace. Using Integer for Hive Table Stats > unfortunately is not going to work. It needs to be a long. I've provided a > patch to fix this. > 09 May 2017 10:24:34,474 ERROR [ambari-client-thread-55044] > ContainerResponse:419 - The RuntimeException could not be mapped to a > response, re-throwing to the HT > TP container > java.lang.NumberFormatException: For input string: "12375183159" > at > java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) > at java.lang.Integer.parseInt(Integer.java:583) > at java.lang.Integer.valueOf(Integer.java:766) > at > org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.getTableStats(TableMetaParserImpl.java:115) > at > org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.parse(TableMetaParserImpl.java:62) > at > org.apache.ambari.view.hive20.resources.browser.DDLProxy.getTableProperties(DDLProxy.java:157) > at > org.apache.ambari.view.hive20.resources.browser.DDLService.getTableInfo(DDLService.java:278) > at sun.reflect.GeneratedMethodAccessor253.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > at > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84) > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542) > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473) > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419) > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409) > at > com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) > at > org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684) > a
[jira] [Updated] (AMBARI-20981) Hive 2.0 View Table Statistics overflows Integer Type convert to Long
[ https://issues.apache.org/jira/browse/AMBARI-20981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-20981: --- Attachment: (was: AMBARI-20962_branch-2.5.patch) > Hive 2.0 View Table Statistics overflows Integer Type convert to Long > - > > Key: AMBARI-20981 > URL: https://issues.apache.org/jira/browse/AMBARI-20981 > Project: Ambari > Issue Type: Bug > Components: contrib >Affects Versions: 2.5.0, 2.5.1, 2.5.2 > Environment: Ambari 2.5.0.x >Reporter: Greg Senia > Labels: views > Attachments: AMBARI-20981_branch-2.5.patch, AMBARI-20981.patch > > > When testing with our extremely large datasets the statistics data returns a > failure and the following stack trace. Using Integer for Hive Table Stats > unfortunately is not going to work. It needs to be a long. I've provided a > patch to fix this. > 09 May 2017 10:24:34,474 ERROR [ambari-client-thread-55044] > ContainerResponse:419 - The RuntimeException could not be mapped to a > response, re-throwing to the HT > TP container > java.lang.NumberFormatException: For input string: "12375183159" > at > java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) > at java.lang.Integer.parseInt(Integer.java:583) > at java.lang.Integer.valueOf(Integer.java:766) > at > org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.getTableStats(TableMetaParserImpl.java:115) > at > org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.parse(TableMetaParserImpl.java:62) > at > org.apache.ambari.view.hive20.resources.browser.DDLProxy.getTableProperties(DDLProxy.java:157) > at > org.apache.ambari.view.hive20.resources.browser.DDLService.getTableInfo(DDLService.java:278) > at sun.reflect.GeneratedMethodAccessor253.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > at > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84) > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542) > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473) > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419) > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409) > at > com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) > at > org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
[jira] [Updated] (AMBARI-20981) Hive 2.0 View Table Statistics overflows Integer Type convert to Long
[ https://issues.apache.org/jira/browse/AMBARI-20981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-20981: --- Attachment: AMBARI-20962_branch-2.5.patch attached AMBARI-20962_branch-2.5.patch : new patch with formatting and message. > Hive 2.0 View Table Statistics overflows Integer Type convert to Long > - > > Key: AMBARI-20981 > URL: https://issues.apache.org/jira/browse/AMBARI-20981 > Project: Ambari > Issue Type: Bug > Components: contrib >Affects Versions: 2.5.0, 2.5.1, 2.5.2 > Environment: Ambari 2.5.0.x >Reporter: Greg Senia > Labels: views > Attachments: AMBARI-20962_branch-2.5.patch, AMBARI-20981.patch > > > When testing with our extremely large datasets the statistics data returns a > failure and the following stack trace. Using Integer for Hive Table Stats > unfortunately is not going to work. It needs to be a long. I've provided a > patch to fix this. > 09 May 2017 10:24:34,474 ERROR [ambari-client-thread-55044] > ContainerResponse:419 - The RuntimeException could not be mapped to a > response, re-throwing to the HT > TP container > java.lang.NumberFormatException: For input string: "12375183159" > at > java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) > at java.lang.Integer.parseInt(Integer.java:583) > at java.lang.Integer.valueOf(Integer.java:766) > at > org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.getTableStats(TableMetaParserImpl.java:115) > at > org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.parse(TableMetaParserImpl.java:62) > at > org.apache.ambari.view.hive20.resources.browser.DDLProxy.getTableProperties(DDLProxy.java:157) > at > org.apache.ambari.view.hive20.resources.browser.DDLService.getTableInfo(DDLService.java:278) > at sun.reflect.GeneratedMethodAccessor253.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > at > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84) > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542) > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473) > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419) > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409) > at > com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) > at >
[jira] [Updated] (AMBARI-20962) Hive View 2.0 and 1.5 : The downloaded file name will be shown as ____.csv when we download the query result with the unicode name
[ https://issues.apache.org/jira/browse/AMBARI-20962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-20962: --- Resolution: Fixed Status: Resolved (was: Patch Available) committed to branch-2.5 and trunk > Hive View 2.0 and 1.5 : The downloaded file name will be shown as .csv > when we download the query result with the unicode name > -- > > Key: AMBARI-20962 > URL: https://issues.apache.org/jira/browse/AMBARI-20962 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.2 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.1 > > Attachments: AMBARI-20962_branch-2.5.patch > > > 1. Execute one hive query using the query editor of hive view and result are > shown > 2. Click "Download as CSV" to download the query result > 3. Type the file name with unicode characters > 4. Wait for the download process completed > Expected result: > The unicode content should be showed in the file name > Acutal Result: > The unicode content is replaced by ___ > The file name change to ___.csv -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20962) Hive View 2.0 and 1.5 : The downloaded file name will be shown as ____.csv when we download the query result with the unicode name
[ https://issues.apache.org/jira/browse/AMBARI-20962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-20962: --- Status: Patch Available (was: Open) > Hive View 2.0 and 1.5 : The downloaded file name will be shown as .csv > when we download the query result with the unicode name > -- > > Key: AMBARI-20962 > URL: https://issues.apache.org/jira/browse/AMBARI-20962 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.2 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.1 > > Attachments: AMBARI-20962_branch-2.5.patch > > > 1. Execute one hive query using the query editor of hive view and result are > shown > 2. Click "Download as CSV" to download the query result > 3. Type the file name with unicode characters > 4. Wait for the download process completed > Expected result: > The unicode content should be showed in the file name > Acutal Result: > The unicode content is replaced by ___ > The file name change to ___.csv -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20962) Hive View 2.0 and 1.5 : The downloaded file name will be shown as ____.csv when we download the query result with the unicode name
[ https://issues.apache.org/jira/browse/AMBARI-20962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-20962: --- Attachment: AMBARI-20962_branch-2.5.patch > Hive View 2.0 and 1.5 : The downloaded file name will be shown as .csv > when we download the query result with the unicode name > -- > > Key: AMBARI-20962 > URL: https://issues.apache.org/jira/browse/AMBARI-20962 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.2 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.1 > > Attachments: AMBARI-20962_branch-2.5.patch > > > 1. Execute one hive query using the query editor of hive view and result are > shown > 2. Click "Download as CSV" to download the query result > 3. Type the file name with unicode characters > 4. Wait for the download process completed > Expected result: > The unicode content should be showed in the file name > Acutal Result: > The unicode content is replaced by ___ > The file name change to ___.csv -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20962) Hive View 2.0 and 1.5 : The downloaded file name will be shown as ____.csv when we download the query result with the unicode name
Nitiraj Singh Rathore created AMBARI-20962: -- Summary: Hive View 2.0 and 1.5 : The downloaded file name will be shown as .csv when we download the query result with the unicode name Key: AMBARI-20962 URL: https://issues.apache.org/jira/browse/AMBARI-20962 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.4.2 Reporter: Nitiraj Singh Rathore Assignee: Nitiraj Singh Rathore Fix For: 2.5.1 1. Execute one hive query using the query editor of hive view and result are shown 2. Click "Download as CSV" to download the query result 3. Type the file name with unicode characters 4. Wait for the download process completed Expected result: The unicode content should be showed in the file name Acutal Result: The unicode content is replaced by ___ The file name change to ___.csv -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20936) Users are not able to login to ambari UI after Ambari upgrade from 2.4.x to 2.5.0
[ https://issues.apache.org/jira/browse/AMBARI-20936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16001578#comment-16001578 ] Nitiraj Singh Rathore commented on AMBARI-20936: committed to branch-2.5 and trunk. > Users are not able to login to ambari UI after Ambari upgrade from 2.4.x to > 2.5.0 > - > > Key: AMBARI-20936 > URL: https://issues.apache.org/jira/browse/AMBARI-20936 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 > Environment: LDAP is configured. > Zeppline view is created and USE permission is given to users. >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.1 > > Attachments: AMBARI-20936_branch-2.5.patch, AMBARI-20936_trunk.patch, > error.log > > > After upgrade from Ambari 2.4 to Ambari 2.5 when LDAP users try to login they > get error and are not able to login. > Attached is log snippet. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20936) Users are not able to login to ambari UI after Ambari upgrade from 2.4.x to 2.5.0
[ https://issues.apache.org/jira/browse/AMBARI-20936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-20936: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Users are not able to login to ambari UI after Ambari upgrade from 2.4.x to > 2.5.0 > - > > Key: AMBARI-20936 > URL: https://issues.apache.org/jira/browse/AMBARI-20936 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 > Environment: LDAP is configured. > Zeppline view is created and USE permission is given to users. >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.1 > > Attachments: AMBARI-20936_branch-2.5.patch, AMBARI-20936_trunk.patch, > error.log > > > After upgrade from Ambari 2.4 to Ambari 2.5 when LDAP users try to login they > get error and are not able to login. > Attached is log snippet. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20936) Users are not able to login to ambari UI after Ambari upgrade from 2.4.x to 2.5.0
[ https://issues.apache.org/jira/browse/AMBARI-20936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16001565#comment-16001565 ] Nitiraj Singh Rathore commented on AMBARI-20936: Uploaded another patch for trunk after removing import order and other conflicts in trunk > Users are not able to login to ambari UI after Ambari upgrade from 2.4.x to > 2.5.0 > - > > Key: AMBARI-20936 > URL: https://issues.apache.org/jira/browse/AMBARI-20936 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 > Environment: LDAP is configured. > Zeppline view is created and USE permission is given to users. >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.1 > > Attachments: AMBARI-20936_branch-2.5.patch, AMBARI-20936_trunk.patch, > error.log > > > After upgrade from Ambari 2.4 to Ambari 2.5 when LDAP users try to login they > get error and are not able to login. > Attached is log snippet. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20936) Users are not able to login to ambari UI after Ambari upgrade from 2.4.x to 2.5.0
[ https://issues.apache.org/jira/browse/AMBARI-20936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-20936: --- Attachment: AMBARI-20936_trunk.patch > Users are not able to login to ambari UI after Ambari upgrade from 2.4.x to > 2.5.0 > - > > Key: AMBARI-20936 > URL: https://issues.apache.org/jira/browse/AMBARI-20936 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 > Environment: LDAP is configured. > Zeppline view is created and USE permission is given to users. >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.1 > > Attachments: AMBARI-20936_branch-2.5.patch, AMBARI-20936_trunk.patch, > error.log > > > After upgrade from Ambari 2.4 to Ambari 2.5 when LDAP users try to login they > get error and are not able to login. > Attached is log snippet. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20936) Users are not able to login to ambari UI after Ambari upgrade from 2.4.x to 2.5.0
[ https://issues.apache.org/jira/browse/AMBARI-20936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15997981#comment-15997981 ] Nitiraj Singh Rathore commented on AMBARI-20936: Instead of deleting entries from DB directly, used uninstalling. Did refactoring to take the DB related code out of the ViewRegistry (which is anyway growing very big and is live object which cannot be used during Upgrade process) to create ViewInstanceOperationHandler.java. > Users are not able to login to ambari UI after Ambari upgrade from 2.4.x to > 2.5.0 > - > > Key: AMBARI-20936 > URL: https://issues.apache.org/jira/browse/AMBARI-20936 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 > Environment: LDAP is configured. > Zeppline view is created and USE permission is given to users. >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.1 > > Attachments: AMBARI-20936_branch-2.5.patch, error.log > > > After upgrade from Ambari 2.4 to Ambari 2.5 when LDAP users try to login they > get error and are not able to login. > Attached is log snippet. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20936) Users are not able to login to ambari UI after Ambari upgrade from 2.4.x to 2.5.0
[ https://issues.apache.org/jira/browse/AMBARI-20936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-20936: --- Status: Patch Available (was: Open) > Users are not able to login to ambari UI after Ambari upgrade from 2.4.x to > 2.5.0 > - > > Key: AMBARI-20936 > URL: https://issues.apache.org/jira/browse/AMBARI-20936 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 > Environment: LDAP is configured. > Zeppline view is created and USE permission is given to users. >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.1 > > Attachments: AMBARI-20936_branch-2.5.patch, error.log > > > After upgrade from Ambari 2.4 to Ambari 2.5 when LDAP users try to login they > get error and are not able to login. > Attached is log snippet. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20936) Users are not able to login to ambari UI after Ambari upgrade from 2.4.x to 2.5.0
[ https://issues.apache.org/jira/browse/AMBARI-20936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-20936: --- Attachment: AMBARI-20936_branch-2.5.patch > Users are not able to login to ambari UI after Ambari upgrade from 2.4.x to > 2.5.0 > - > > Key: AMBARI-20936 > URL: https://issues.apache.org/jira/browse/AMBARI-20936 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 > Environment: LDAP is configured. > Zeppline view is created and USE permission is given to users. >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.1 > > Attachments: AMBARI-20936_branch-2.5.patch, error.log > > > After upgrade from Ambari 2.4 to Ambari 2.5 when LDAP users try to login they > get error and are not able to login. > Attached is log snippet. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20936) Users are not able to login to ambari UI after Ambari upgrade from 2.4.x to 2.5.0
[ https://issues.apache.org/jira/browse/AMBARI-20936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-20936: --- Fix Version/s: (was: 2.5.0) 2.5.1 > Users are not able to login to ambari UI after Ambari upgrade from 2.4.x to > 2.5.0 > - > > Key: AMBARI-20936 > URL: https://issues.apache.org/jira/browse/AMBARI-20936 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 > Environment: LDAP is configured. > Zeppline view is created and USE permission is given to users. >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.1 > > Attachments: error.log > > > After upgrade from Ambari 2.4 to Ambari 2.5 when LDAP users try to login they > get error and are not able to login. > Attached is log snippet. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20936) Users are not able to login to ambari UI after Ambari upgrade from 2.4.x to 2.5.0
[ https://issues.apache.org/jira/browse/AMBARI-20936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-20936: --- Affects Version/s: (was: 2.5.0) 2.5.1 > Users are not able to login to ambari UI after Ambari upgrade from 2.4.x to > 2.5.0 > - > > Key: AMBARI-20936 > URL: https://issues.apache.org/jira/browse/AMBARI-20936 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 > Environment: LDAP is configured. > Zeppline view is created and USE permission is given to users. >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.1 > > Attachments: error.log > > > After upgrade from Ambari 2.4 to Ambari 2.5 when LDAP users try to login they > get error and are not able to login. > Attached is log snippet. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20936) Users are not able to login to ambari UI after Ambari upgrade from 2.4.x to 2.5.0
[ https://issues.apache.org/jira/browse/AMBARI-20936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15997145#comment-15997145 ] Nitiraj Singh Rathore commented on AMBARI-20936: The reason was that there some left over entries of zeppline view in adminprivilege table. The proposed work around of the problem. SELECT adminresource.resource_id FROM adminresource LEFT OUTER JOIN viewinstance USING (resource_id) WHERE adminresource.resource_type_id > 5 AND viewinstance.view_instance_id IS NULL; If this returns any resources, those are orphaned are causing the NPE. You'll have to remove them. DELETE FROM adminresources WHERE resource_id IN (); DELETE FROM adminprivilege WHERE resource_id IN (); CC: [~u39kun] > Users are not able to login to ambari UI after Ambari upgrade from 2.4.x to > 2.5.0 > - > > Key: AMBARI-20936 > URL: https://issues.apache.org/jira/browse/AMBARI-20936 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 > Environment: LDAP is configured. > Zeppline view is created and USE permission is given to users. >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.0 > > Attachments: error.log > > > After upgrade from Ambari 2.4 to Ambari 2.5 when LDAP users try to login they > get error and are not able to login. > Attached is log snippet. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20936) Users are not able to login to ambari UI after Ambari upgrade from 2.4.x to 2.5.0
[ https://issues.apache.org/jira/browse/AMBARI-20936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-20936: --- Attachment: error.log > Users are not able to login to ambari UI after Ambari upgrade from 2.4.x to > 2.5.0 > - > > Key: AMBARI-20936 > URL: https://issues.apache.org/jira/browse/AMBARI-20936 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 > Environment: LDAP is configured. > Zeppline view is created and USE permission is given to users. >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.0 > > Attachments: error.log > > > After upgrade from Ambari 2.4 to Ambari 2.5 when LDAP users try to login they > get error and are not able to login. > Attached is log snippet. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20936) Users are not able to login to ambari UI after Ambari upgrade from 2.4.x to 2.5.0
Nitiraj Singh Rathore created AMBARI-20936: -- Summary: Users are not able to login to ambari UI after Ambari upgrade from 2.4.x to 2.5.0 Key: AMBARI-20936 URL: https://issues.apache.org/jira/browse/AMBARI-20936 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Environment: LDAP is configured. Zeppline view is created and USE permission is given to users. Reporter: Nitiraj Singh Rathore Assignee: Nitiraj Singh Rathore Fix For: 2.5.0 After upgrade from Ambari 2.4 to Ambari 2.5 when LDAP users try to login they get error and are not able to login. Attached is log snippet. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20905) Smartsense view do not load and shows blank
[ https://issues.apache.org/jira/browse/AMBARI-20905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-20905: --- Fix Version/s: (was: 2.5.1) > Smartsense view do not load and shows blank > --- > > Key: AMBARI-20905 > URL: https://issues.apache.org/jira/browse/AMBARI-20905 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Attachments: AMBARI-20905_branch-2.5.patch > > > Seems like smartsense view picks up the wrong cluster Id. > 22 Mar 2017 16:21:58,994 ERROR [ambari-client-thread-115] > ContainerResponse:419 - The RuntimeException could not be mapped to a > response, re-throwing to the HTTP container > org.apache.ambari.server.view.IllegalClusterException: Failed to get cluster > information associated with this view instance > at > org.apache.ambari.server.view.ViewRegistry.getCluster(ViewRegistry.java:937) > at > org.apache.ambari.server.view.ViewContextImpl.getCluster(ViewContextImpl.java:370) > at > org.apache.ambari.server.view.ViewContextImpl.getPropertyValues(ViewContextImpl.java:437) > at > org.apache.ambari.server.view.ViewContextImpl.getProperties(ViewContextImpl.java:171) > at > com.hortonworks.support.tools.view.ServerProxy.buildHeaders(ServerProxy.java:243) > at > com.hortonworks.support.tools.view.ServerProxy.execute(ServerProxy.java:133) > at > com.hortonworks.support.tools.view.ServerProxy.execute(ServerProxy.java:112) > at > com.hortonworks.support.tools.view.ServerProxy.execute(ServerProxy.java:94) > at > com.hortonworks.support.tools.view.ServerResource.getContext(ServerResource.java:54) > at sun.reflect.GeneratedMethodAccessor225.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > at > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84) > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542) > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473) > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419) > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409) > at > com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at > org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1507) > at > org.sp
[jira] [Updated] (AMBARI-20905) Smartsense view do not load and shows blank
[ https://issues.apache.org/jira/browse/AMBARI-20905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-20905: --- Status: Open (was: Patch Available) As per review comments lets try to find root cause and correct it there. So cancelling this patch. > Smartsense view do not load and shows blank > --- > > Key: AMBARI-20905 > URL: https://issues.apache.org/jira/browse/AMBARI-20905 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.1 > > Attachments: AMBARI-20905_branch-2.5.patch > > > Seems like smartsense view picks up the wrong cluster Id. > 22 Mar 2017 16:21:58,994 ERROR [ambari-client-thread-115] > ContainerResponse:419 - The RuntimeException could not be mapped to a > response, re-throwing to the HTTP container > org.apache.ambari.server.view.IllegalClusterException: Failed to get cluster > information associated with this view instance > at > org.apache.ambari.server.view.ViewRegistry.getCluster(ViewRegistry.java:937) > at > org.apache.ambari.server.view.ViewContextImpl.getCluster(ViewContextImpl.java:370) > at > org.apache.ambari.server.view.ViewContextImpl.getPropertyValues(ViewContextImpl.java:437) > at > org.apache.ambari.server.view.ViewContextImpl.getProperties(ViewContextImpl.java:171) > at > com.hortonworks.support.tools.view.ServerProxy.buildHeaders(ServerProxy.java:243) > at > com.hortonworks.support.tools.view.ServerProxy.execute(ServerProxy.java:133) > at > com.hortonworks.support.tools.view.ServerProxy.execute(ServerProxy.java:112) > at > com.hortonworks.support.tools.view.ServerProxy.execute(ServerProxy.java:94) > at > com.hortonworks.support.tools.view.ServerResource.getContext(ServerResource.java:54) > at sun.reflect.GeneratedMethodAccessor225.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > at > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84) > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542) > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473) > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419) > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409) > at > com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at > org.eclipse.jetty.servlet.ServletHolder.handle(ServletHo
[jira] [Updated] (AMBARI-20906) Sometimes: Command [ambari-server restart] failed after upgrade Smartsense (Upgrade from 2.4.1.0 to 2.5.0.1)
[ https://issues.apache.org/jira/browse/AMBARI-20906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-20906: --- Resolution: Fixed Status: Resolved (was: Patch Available) committed to branch-2.5 and trunk > Sometimes: Command [ambari-server restart] failed after upgrade Smartsense > (Upgrade from 2.4.1.0 to 2.5.0.1) > > > Key: AMBARI-20906 > URL: https://issues.apache.org/jira/browse/AMBARI-20906 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.1 > > Attachments: AMBARI-20906_branch-2.5.patch > > > 30 Mar 2017 04:05:25,717 ERROR [pool-5-thread-1] > AmbariJpaLocalTxnInterceptor:180 - [DETAILED ERROR] Rollback reason: > Local Exception Stack: > Exception [EclipseLink-7251] (Eclipse Persistence Services - > 2.6.2.v20151217-774c696): > org.eclipse.persistence.exceptions.ValidationException > Exception Description: The attribute [viewInstance] of class > [org.apache.ambari.server.orm.entities.ViewInstancePropertyEntity] is mapped > to a primary key column in the database. Updates are not allowed. > at > org.eclipse.persistence.exceptions.ValidationException.primaryKeyUpdateDisallowed(ValidationException.java:2551) > at > org.eclipse.persistence.mappings.OneToOneMapping.writeFromObjectIntoRowWithChangeRecord(OneToOneMapping.java:2035) > at > org.eclipse.persistence.internal.descriptors.ObjectBuilder.buildRowForUpdateWithChangeSet(ObjectBuilder.java:1769) > at > org.eclipse.persistence.internal.queries.DatabaseQueryMechanism.updateObjectForWriteWithChangeSet(DatabaseQueryMechanism.java:1030) > at > org.eclipse.persistence.queries.UpdateObjectQuery.executeCommitWithChangeSet(UpdateObjectQuery.java:84) > at > org.eclipse.persistence.internal.queries.DatabaseQueryMechanism.executeWriteWithChangeSet(DatabaseQueryMechanism.java:301) > at > org.eclipse.persistence.queries.WriteObjectQuery.executeDatabaseQuery(WriteObjectQuery.java:58) > at > org.eclipse.persistence.queries.DatabaseQuery.execute(DatabaseQuery.java:904) > at > org.eclipse.persistence.queries.DatabaseQuery.executeInUnitOfWork(DatabaseQuery.java:803) > at > org.eclipse.persistence.queries.ObjectLevelModifyQuery.executeInUnitOfWorkObjectLevelModifyQuery(ObjectLevelModifyQuery.java:108) > at > org.eclipse.persistence.queries.ObjectLevelModifyQuery.executeInUnitOfWork(ObjectLevelModifyQuery.java:85) > at > org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.internalExecuteQuery(UnitOfWorkImpl.java:2896) > at > org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1857) > at > org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1839) > at > org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1790) > at > org.eclipse.persistence.internal.sessions.CommitManager.commitChangedObjectsForClassWithChangeSet(CommitManager.java:273) > at > org.eclipse.persistence.internal.sessions.CommitManager.commitAllObjectsForClassWithChangeSet(CommitManager.java:193) > at > org.eclipse.persistence.internal.sessions.CommitManager.commitAllObjectsWithChangeSet(CommitManager.java:139) > at > org.eclipse.persistence.internal.sessions.AbstractSession.writeAllObjectsWithChangeSet(AbstractSession.java:4263) > at > org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitToDatabase(UnitOfWorkImpl.java:1441) > at > org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitToDatabaseWithChangeSet(UnitOfWorkImpl.java:1531) > at > org.eclipse.persistence.internal.sessions.RepeatableWriteUnitOfWork.commitRootUnitOfWork(RepeatableWriteUnitOfWork.java:278) > at > org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitAndResume(UnitOfWorkImpl.java:1169) > at > org.eclipse.persistence.internal.jpa.transaction.EntityTransactionImpl.commit(EntityTransactionImpl.java:134) > at > org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:153) > at > com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:72) > at > com.google.inject.internal.InterceptorStackCallback.intercept(InterceptorStackCallback.java:52) > at > org.apache.ambari.server.view.ViewRegistry$$EnhancerByGuice$$7c0d3646.mergeViewInstance() > at > org.apache.ambari.server.view.ViewRegistry.installViewInstance(ViewRegistry.java:582) >
[jira] [Assigned] (AMBARI-20905) Smartsense view do not load and shows blank
[ https://issues.apache.org/jira/browse/AMBARI-20905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore reassigned AMBARI-20905: -- Assignee: Nitiraj Singh Rathore > Smartsense view do not load and shows blank > --- > > Key: AMBARI-20905 > URL: https://issues.apache.org/jira/browse/AMBARI-20905 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.1 > > Attachments: AMBARI-20905_branch-2.5.patch > > > Seems like smartsense view picks up the wrong cluster Id. > 22 Mar 2017 16:21:58,994 ERROR [ambari-client-thread-115] > ContainerResponse:419 - The RuntimeException could not be mapped to a > response, re-throwing to the HTTP container > org.apache.ambari.server.view.IllegalClusterException: Failed to get cluster > information associated with this view instance > at > org.apache.ambari.server.view.ViewRegistry.getCluster(ViewRegistry.java:937) > at > org.apache.ambari.server.view.ViewContextImpl.getCluster(ViewContextImpl.java:370) > at > org.apache.ambari.server.view.ViewContextImpl.getPropertyValues(ViewContextImpl.java:437) > at > org.apache.ambari.server.view.ViewContextImpl.getProperties(ViewContextImpl.java:171) > at > com.hortonworks.support.tools.view.ServerProxy.buildHeaders(ServerProxy.java:243) > at > com.hortonworks.support.tools.view.ServerProxy.execute(ServerProxy.java:133) > at > com.hortonworks.support.tools.view.ServerProxy.execute(ServerProxy.java:112) > at > com.hortonworks.support.tools.view.ServerProxy.execute(ServerProxy.java:94) > at > com.hortonworks.support.tools.view.ServerResource.getContext(ServerResource.java:54) > at sun.reflect.GeneratedMethodAccessor225.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > at > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84) > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542) > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473) > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419) > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409) > at > com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at > org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletH
[jira] [Updated] (AMBARI-20906) Sometimes: Command [ambari-server restart] failed after upgrade Smartsense (Upgrade from 2.4.1.0 to 2.5.0.1)
[ https://issues.apache.org/jira/browse/AMBARI-20906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-20906: --- Status: Patch Available (was: Open) > Sometimes: Command [ambari-server restart] failed after upgrade Smartsense > (Upgrade from 2.4.1.0 to 2.5.0.1) > > > Key: AMBARI-20906 > URL: https://issues.apache.org/jira/browse/AMBARI-20906 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.1 > > Attachments: AMBARI-20906_branch-2.5.patch > > > 30 Mar 2017 04:05:25,717 ERROR [pool-5-thread-1] > AmbariJpaLocalTxnInterceptor:180 - [DETAILED ERROR] Rollback reason: > Local Exception Stack: > Exception [EclipseLink-7251] (Eclipse Persistence Services - > 2.6.2.v20151217-774c696): > org.eclipse.persistence.exceptions.ValidationException > Exception Description: The attribute [viewInstance] of class > [org.apache.ambari.server.orm.entities.ViewInstancePropertyEntity] is mapped > to a primary key column in the database. Updates are not allowed. > at > org.eclipse.persistence.exceptions.ValidationException.primaryKeyUpdateDisallowed(ValidationException.java:2551) > at > org.eclipse.persistence.mappings.OneToOneMapping.writeFromObjectIntoRowWithChangeRecord(OneToOneMapping.java:2035) > at > org.eclipse.persistence.internal.descriptors.ObjectBuilder.buildRowForUpdateWithChangeSet(ObjectBuilder.java:1769) > at > org.eclipse.persistence.internal.queries.DatabaseQueryMechanism.updateObjectForWriteWithChangeSet(DatabaseQueryMechanism.java:1030) > at > org.eclipse.persistence.queries.UpdateObjectQuery.executeCommitWithChangeSet(UpdateObjectQuery.java:84) > at > org.eclipse.persistence.internal.queries.DatabaseQueryMechanism.executeWriteWithChangeSet(DatabaseQueryMechanism.java:301) > at > org.eclipse.persistence.queries.WriteObjectQuery.executeDatabaseQuery(WriteObjectQuery.java:58) > at > org.eclipse.persistence.queries.DatabaseQuery.execute(DatabaseQuery.java:904) > at > org.eclipse.persistence.queries.DatabaseQuery.executeInUnitOfWork(DatabaseQuery.java:803) > at > org.eclipse.persistence.queries.ObjectLevelModifyQuery.executeInUnitOfWorkObjectLevelModifyQuery(ObjectLevelModifyQuery.java:108) > at > org.eclipse.persistence.queries.ObjectLevelModifyQuery.executeInUnitOfWork(ObjectLevelModifyQuery.java:85) > at > org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.internalExecuteQuery(UnitOfWorkImpl.java:2896) > at > org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1857) > at > org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1839) > at > org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1790) > at > org.eclipse.persistence.internal.sessions.CommitManager.commitChangedObjectsForClassWithChangeSet(CommitManager.java:273) > at > org.eclipse.persistence.internal.sessions.CommitManager.commitAllObjectsForClassWithChangeSet(CommitManager.java:193) > at > org.eclipse.persistence.internal.sessions.CommitManager.commitAllObjectsWithChangeSet(CommitManager.java:139) > at > org.eclipse.persistence.internal.sessions.AbstractSession.writeAllObjectsWithChangeSet(AbstractSession.java:4263) > at > org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitToDatabase(UnitOfWorkImpl.java:1441) > at > org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitToDatabaseWithChangeSet(UnitOfWorkImpl.java:1531) > at > org.eclipse.persistence.internal.sessions.RepeatableWriteUnitOfWork.commitRootUnitOfWork(RepeatableWriteUnitOfWork.java:278) > at > org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitAndResume(UnitOfWorkImpl.java:1169) > at > org.eclipse.persistence.internal.jpa.transaction.EntityTransactionImpl.commit(EntityTransactionImpl.java:134) > at > org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:153) > at > com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:72) > at > com.google.inject.internal.InterceptorStackCallback.intercept(InterceptorStackCallback.java:52) > at > org.apache.ambari.server.view.ViewRegistry$$EnhancerByGuice$$7c0d3646.mergeViewInstance() > at > org.apache.ambari.server.view.ViewRegistry.installViewInstance(ViewRegistry.java:582) > at > org.apache.ambari.server.view.ViewRegistry.installAutoInsta
