[jira] [Commented] (AMBARI-24792) Infra Manager: not all the documents archived
[ https://issues.apache.org/jira/browse/AMBARI-24792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16654696#comment-16654696 ] ASF GitHub Bot commented on AMBARI-24792: - asfgit commented on issue #8: AMBARI-24792 - Infra Manager: not all the documents archived URL: https://github.com/apache/ambari-infra/pull/8#issuecomment-430890110 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/Ambari-Infra-Github-PR-Builder/12/ Test PASSed. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Infra Manager: not all the documents archived > - > > Key: AMBARI-24792 > URL: https://issues.apache.org/jira/browse/AMBARI-24792 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 2.8.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > > Infra manager does not use the sort_column properties when reading the > documents to archive. This leads to some of the documents are not exported. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24792) Infra Manager: not all the documents archived
[ https://issues.apache.org/jira/browse/AMBARI-24792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24792: Labels: pull-request-available (was: ) > Infra Manager: not all the documents archived > - > > Key: AMBARI-24792 > URL: https://issues.apache.org/jira/browse/AMBARI-24792 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 2.8.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > > Infra manager does not use the sort_column properties when reading the > documents to archive. This leads to some of the documents are not exported. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24792) Infra Manager: not all the documents archived
[ https://issues.apache.org/jira/browse/AMBARI-24792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16654695#comment-16654695 ] ASF GitHub Bot commented on AMBARI-24792: - kasakrisz opened a new pull request #8: AMBARI-24792 - Infra Manager: not all the documents archived URL: https://github.com/apache/ambari-infra/pull/8 ## What changes were proposed in this pull request? 1. Infra manager did not use the sort_column properties when reading the documents to archive. This lead to some of the documents are not exported when the read block size was less than the number of documents to export and no sort_column were specified by job parameters. Fix: copy the sort_column properties to the actual ArchivingParameters instance if job parameters are not given. 2. Add integration test to check if all the documents are archived. ## How was this patch tested? UTs and ITs passed. Manually: 1. Deploy Ambari and a cluster including infra solr, zookeeper, logsearch to a vagrant env 2. When service logs collection has some documents stop Logsearch after a while to prevent producing more service log documents. 3. Run Infra Manager from Idea 4. Start `archive_service_logs` job by specifying an interval end value of now, a read block size smaller than the service logs collection size and a local destination only 5. Check the files in the local folder contains all the documents were stored in service logs and service logs collection is empty in Solr This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Infra Manager: not all the documents archived > - > > Key: AMBARI-24792 > URL: https://issues.apache.org/jira/browse/AMBARI-24792 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 2.8.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > > Infra manager does not use the sort_column properties when reading the > documents to archive. This leads to some of the documents are not exported. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24775) Configuration warning: insert a space char between label value and unit-name
[
https://issues.apache.org/jira/browse/AMBARI-24775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Krisztian Kasa updated AMBARI-24775:
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Configuration warning: insert a space char between label value and unit-name
>
>
> Key: AMBARI-24775
> URL: https://issues.apache.org/jira/browse/AMBARI-24775
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.8.0
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> On Ambari enhanced UI configuration and Configuration warning page inserting
> a space character between label value and unit-name when it is shown as a
> warning tooltip and text.
> from
> {code}
> 2days
> 100GB
> {code}
> to
> {code}
> 2 days
> 100 GB
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24777) Infra Manager: Remove dependencies due to security concerns.
[ https://issues.apache.org/jira/browse/AMBARI-24777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krisztian Kasa updated AMBARI-24777: Resolution: Fixed Status: Resolved (was: Patch Available) > Infra Manager: Remove dependencies due to security concerns. > > > Key: AMBARI-24777 > URL: https://issues.apache.org/jira/browse/AMBARI-24777 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 2.8.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24800) service adviser changes for cluster specific configs
[ https://issues.apache.org/jira/browse/AMBARI-24800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-24800: --- Status: Patch Available (was: Open) > service adviser changes for cluster specific configs > > > Key: AMBARI-24800 > URL: https://issues.apache.org/jira/browse/AMBARI-24800 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Env: HDC Spark Data science (m4x4xlarge 16 CPU/64 GB) > Spark defaults aren't changed in ambari. It is loading with 1 GB > spark.executor.memory. > (Should this be 60-70% of yarn min container size. Need to consider > spark.yarn.executor.memoryOverhead) > Add such logic for "spark.shuffle.io.numConnectionsPerPeer": > spark.shuffle.io.numConnectionsPerPeer should be configured dynamically based > on cluster size. > Recommandation was to set it to 10 if number of nodes < 10 and remove (so > that default value is used) for higher values. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24800) service adviser changes for cluster specific configs
[ https://issues.apache.org/jira/browse/AMBARI-24800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24800: Labels: pull-request-available (was: ) > service adviser changes for cluster specific configs > > > Key: AMBARI-24800 > URL: https://issues.apache.org/jira/browse/AMBARI-24800 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Labels: pull-request-available > Fix For: 2.8.0 > > > Env: HDC Spark Data science (m4x4xlarge 16 CPU/64 GB) > Spark defaults aren't changed in ambari. It is loading with 1 GB > spark.executor.memory. > (Should this be 60-70% of yarn min container size. Need to consider > spark.yarn.executor.memoryOverhead) > Add such logic for "spark.shuffle.io.numConnectionsPerPeer": > spark.shuffle.io.numConnectionsPerPeer should be configured dynamically based > on cluster size. > Recommandation was to set it to 10 if number of nodes < 10 and remove (so > that default value is used) for higher values. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24800) service adviser changes for cluster specific configs
Vitaly Brodetskyi created AMBARI-24800: -- Summary: service adviser changes for cluster specific configs Key: AMBARI-24800 URL: https://issues.apache.org/jira/browse/AMBARI-24800 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Vitaly Brodetskyi Assignee: Vitaly Brodetskyi Fix For: 2.8.0 Env: HDC Spark Data science (m4x4xlarge 16 CPU/64 GB) Spark defaults aren't changed in ambari. It is loading with 1 GB spark.executor.memory. (Should this be 60-70% of yarn min container size. Need to consider spark.yarn.executor.memoryOverhead) Add such logic for "spark.shuffle.io.numConnectionsPerPeer": spark.shuffle.io.numConnectionsPerPeer should be configured dynamically based on cluster size. Recommandation was to set it to 10 if number of nodes < 10 and remove (so that default value is used) for higher values. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24797) Support regex based metric inclusion in KafkaTimelineMetricsReporter
[ https://issues.apache.org/jira/browse/AMBARI-24797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16654256#comment-16654256 ] ASF GitHub Bot commented on AMBARI-24797: - asfgit commented on issue #8: [AMBARI-24797] Support regex based metric inclusion in KafkaTimelineM… URL: https://github.com/apache/ambari-metrics/pull/8#issuecomment-430801735 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/Ambari-Metrics-Github-PR-Builder/19/ Test PASSed. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Support regex based metric inclusion in KafkaTimelineMetricsReporter > > > Key: AMBARI-24797 > URL: https://issues.apache.org/jira/browse/AMBARI-24797 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.8.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > > The request is to to add an additional config property > *external.kafka.metrics.include.regex* to include metrics based on regex > patterns. This property can take multiple comma separated regex expressions. > Implementation Logic > * By default, a metric will be included. > * If the metric starts with any of the prefixes in the exclude.prefix > property, it is a candidate for discarding. > * However, for an "excluded" metric, if the metric starts with any of the > prefixes in include.prefix or matches any pattern in include.regex, it will > NOT be discarded. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24799) Fix jetty CVEs for Log Search (2.7.x)
[ https://issues.apache.org/jira/browse/AMBARI-24799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16654242#comment-16654242 ] Hudson commented on AMBARI-24799: - SUCCESS: Integrated in Jenkins build Ambari-LogSearch-master-Commit #14 (See [https://builds.apache.org/job/Ambari-LogSearch-master-Commit/14/]) AMBARI-24799. Update Spring versions (oleewere: [https://gitbox.apache.org/repos/asf?p=ambari-logsearch.git&a=commit&h=3f317656f12efd3249a7299d3501e56f88b36866]) * (edit) ambari-logsearch-logfeeder/pom.xml * (edit) ambari-logsearch-server/pom.xml > Fix jetty CVEs for Log Search (2.7.x) > - > > Key: AMBARI-24799 > URL: https://issues.apache.org/jira/browse/AMBARI-24799 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 10m > Remaining Estimate: 0h > > See: > - CVE-2018-12536 > - CVE-2017-9735 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24797) Support regex based metric inclusion in KafkaTimelineMetricsReporter
[ https://issues.apache.org/jira/browse/AMBARI-24797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16654239#comment-16654239 ] ASF GitHub Bot commented on AMBARI-24797: - avijayanhwx commented on issue #8: [AMBARI-24797] Support regex based metric inclusion in KafkaTimelineM… URL: https://github.com/apache/ambari-metrics/pull/8#issuecomment-430798757 retest this please. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Support regex based metric inclusion in KafkaTimelineMetricsReporter > > > Key: AMBARI-24797 > URL: https://issues.apache.org/jira/browse/AMBARI-24797 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.8.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > > The request is to to add an additional config property > *external.kafka.metrics.include.regex* to include metrics based on regex > patterns. This property can take multiple comma separated regex expressions. > Implementation Logic > * By default, a metric will be included. > * If the metric starts with any of the prefixes in the exclude.prefix > property, it is a candidate for discarding. > * However, for an "excluded" metric, if the metric starts with any of the > prefixes in include.prefix or matches any pattern in include.regex, it will > NOT be discarded. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24799) Fix jetty CVEs for Log Search (2.7.x)
[ https://issues.apache.org/jira/browse/AMBARI-24799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24799: Labels: pull-request-available (was: ) > Fix jetty CVEs for Log Search (2.7.x) > - > > Key: AMBARI-24799 > URL: https://issues.apache.org/jira/browse/AMBARI-24799 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > > See: > - CVE-2018-12536 > - CVE-2017-9735 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24799) Fix jetty CVEs for Log Search (2.7.x)
[ https://issues.apache.org/jira/browse/AMBARI-24799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-24799: -- Description: See: - CVE-2018-12536 - CVE-2017-9735 > Fix jetty CVEs for Log Search (2.7.x) > - > > Key: AMBARI-24799 > URL: https://issues.apache.org/jira/browse/AMBARI-24799 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Fix For: 2.7.3 > > > See: > - CVE-2018-12536 > - CVE-2017-9735 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24799) Fix jetty CVEs for Log Search (2.7.x)
[ https://issues.apache.org/jira/browse/AMBARI-24799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-24799: -- Summary: Fix jetty CVEs for Log Search (2.7.x) (was: FIx jetty CVEs for Log Search (2.7.x)) > Fix jetty CVEs for Log Search (2.7.x) > - > > Key: AMBARI-24799 > URL: https://issues.apache.org/jira/browse/AMBARI-24799 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Fix For: 2.7.3 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24799) FIx jetty CVEs for Log Search (2.7.x)
Olivér Szabó created AMBARI-24799: - Summary: FIx jetty CVEs for Log Search (2.7.x) Key: AMBARI-24799 URL: https://issues.apache.org/jira/browse/AMBARI-24799 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 2.7.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 2.7.3 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24797) Support regex based metric inclusion in KafkaTimelineMetricsReporter
[ https://issues.apache.org/jira/browse/AMBARI-24797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16654169#comment-16654169 ] ASF GitHub Bot commented on AMBARI-24797: - asfgit commented on issue #8: [AMBARI-24797] Support regex based metric inclusion in KafkaTimelineM… URL: https://github.com/apache/ambari-metrics/pull/8#issuecomment-430785544 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/Ambari-Metrics-Github-PR-Builder/18/ Test FAILed. Test FAILured. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Support regex based metric inclusion in KafkaTimelineMetricsReporter > > > Key: AMBARI-24797 > URL: https://issues.apache.org/jira/browse/AMBARI-24797 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.8.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > > The request is to to add an additional config property > *external.kafka.metrics.include.regex* to include metrics based on regex > patterns. This property can take multiple comma separated regex expressions. > Implementation Logic > * By default, a metric will be included. > * If the metric starts with any of the prefixes in the exclude.prefix > property, it is a candidate for discarding. > * However, for an "excluded" metric, if the metric starts with any of the > prefixes in include.prefix or matches any pattern in include.regex, it will > NOT be discarded. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24797) Support regex based metric inclusion in KafkaTimelineMetricsReporter
[ https://issues.apache.org/jira/browse/AMBARI-24797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16654165#comment-16654165 ] ASF GitHub Bot commented on AMBARI-24797: - avijayanhwx opened a new pull request #8: [AMBARI-24797] Support regex based metric inclusion in KafkaTimelineM… URL: https://github.com/apache/ambari-metrics/pull/8 …etricsReporter. ## What changes were proposed in this pull request? The request is to to add an additional config property external.kafka.metrics.include.regex to include metrics based on regex patterns. This property can take multiple comma separated regex expressions. **Implementation Logic** - By default, a metric will be included. - If the metric starts with any of the prefixes in the exclude.prefix property, it is a candidate for discarding. - However, for an "excluded" metric, if the metric starts with any of the prefixes in include.prefix or matches any pattern in include.regex, it will NOT be discarded. ## How was this patch tested? Manual and unit testing. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Support regex based metric inclusion in KafkaTimelineMetricsReporter > > > Key: AMBARI-24797 > URL: https://issues.apache.org/jira/browse/AMBARI-24797 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.8.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > > The request is to to add an additional config property > *external.kafka.metrics.include.regex* to include metrics based on regex > patterns. This property can take multiple comma separated regex expressions. > Implementation Logic > * By default, a metric will be included. > * If the metric starts with any of the prefixes in the exclude.prefix > property, it is a candidate for discarding. > * However, for an "excluded" metric, if the metric starts with any of the > prefixes in include.prefix or matches any pattern in include.regex, it will > NOT be discarded. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24797) Support regex based metric inclusion in KafkaTimelineMetricsReporter
[ https://issues.apache.org/jira/browse/AMBARI-24797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24797: Labels: pull-request-available (was: ) > Support regex based metric inclusion in KafkaTimelineMetricsReporter > > > Key: AMBARI-24797 > URL: https://issues.apache.org/jira/browse/AMBARI-24797 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.8.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > > The request is to to add an additional config property > *external.kafka.metrics.include.regex* to include metrics based on regex > patterns. This property can take multiple comma separated regex expressions. > Implementation Logic > * By default, a metric will be included. > * If the metric starts with any of the prefixes in the exclude.prefix > property, it is a candidate for discarding. > * However, for an "excluded" metric, if the metric starts with any of the > prefixes in include.prefix or matches any pattern in include.regex, it will > NOT be discarded. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24798) Stack api for services should return if a service is tech preview and warning message content to be displayed
Madhuvanthi Radhakrishnan created AMBARI-24798: -- Summary: Stack api for services should return if a service is tech preview and warning message content to be displayed Key: AMBARI-24798 URL: https://issues.apache.org/jira/browse/AMBARI-24798 Project: Ambari Issue Type: Bug Affects Versions: 2.8.0 Reporter: Madhuvanthi Radhakrishnan Assignee: Madhuvanthi Radhakrishnan Fix For: 2.8.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24797) Support regex based metric inclusion in KafkaTimelineMetricsReporter
Aravindan Vijayan created AMBARI-24797: -- Summary: Support regex based metric inclusion in KafkaTimelineMetricsReporter Key: AMBARI-24797 URL: https://issues.apache.org/jira/browse/AMBARI-24797 Project: Ambari Issue Type: Task Components: ambari-metrics Affects Versions: 2.8.0 Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Fix For: 2.8.0 The request is to to add an additional config property *external.kafka.metrics.include.regex* to include metrics based on regex patterns. This property can take multiple comma separated regex expressions. Implementation Logic * By default, a metric will be included. * If the metric starts with any of the prefixes in the exclude.prefix property, it is a candidate for discarding. * However, for an "excluded" metric, if the metric starts with any of the prefixes in include.prefix or matches any pattern in include.regex, it will NOT be discarded. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24771) Fix CVE issues for Ambari Metrics (2.7.3)
[ https://issues.apache.org/jira/browse/AMBARI-24771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-24771. Resolution: Fixed > Fix CVE issues for Ambari Metrics (2.7.3) > - > > Key: AMBARI-24771 > URL: https://issues.apache.org/jira/browse/AMBARI-24771 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.7.3 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24790) Restart Masters for Service Restart
[ https://issues.apache.org/jira/browse/AMBARI-24790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt resolved AMBARI-24790. -- Resolution: Fixed > Restart Masters for Service Restart > --- > > Key: AMBARI-24790 > URL: https://issues.apache.org/jira/browse/AMBARI-24790 > Project: Ambari > Issue Type: Task > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24795) Allow skipping Python unit tests
[
https://issues.apache.org/jira/browse/AMBARI-24795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-24795:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Allow skipping Python unit tests
>
>
> Key: AMBARI-24795
> URL: https://issues.apache.org/jira/browse/AMBARI-24795
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-agent
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {{ambari-server}} Python tests can be skipped by passing
> {{-DskipPythonTests}} to Maven. The goal of this task is to allow the same
> for {{ambari-agent}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24795) Allow skipping Python unit tests
[
https://issues.apache.org/jira/browse/AMBARI-24795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16653892#comment-16653892
]
Hudson commented on AMBARI-24795:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10226 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/10226/])
AMBARI-24795. Allow skipping Python unit tests (#2482) (github:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=a8200b9bc31224190f8985a6ac8a9e910ac263e7])
* (edit) ambari-server/pom.xml
* (edit) ambari-agent/pom.xml
* (edit) ambari-project/pom.xml
> Allow skipping Python unit tests
>
>
> Key: AMBARI-24795
> URL: https://issues.apache.org/jira/browse/AMBARI-24795
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-agent
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {{ambari-server}} Python tests can be skipped by passing
> {{-DskipPythonTests}} to Maven. The goal of this task is to allow the same
> for {{ambari-agent}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24796) Intermittent CredentialStoreTest test failure
Myroslav Papirkovskyi created AMBARI-24796:
--
Summary: Intermittent CredentialStoreTest test failure
Key: AMBARI-24796
URL: https://issues.apache.org/jira/browse/AMBARI-24796
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.8.0
Reporter: Myroslav Papirkovskyi
Assignee: Myroslav Papirkovskyi
Fix For: 3.0.0
Stacktrace
{code}
java.lang.NullPointerException
at
org.apache.ambari.server.security.encryption.CredentialStoreTest.getExpiredCredentialTest(CredentialStoreTest.java:169)
at
org.apache.ambari.server.security.encryption.CredentialStoreTest.testInMemoryCredentialStoreService_CredentialExpired(CredentialStoreTest.java:90)
{code}
Standard Output
{code}
2018-10-12 14:06:26,230 INFO [main] encryption.MasterKeyServiceImpl
(MasterKeyServiceImpl.java:initializeFromFile(277)) - Loading from persistent
master: #1.0# Fri, Oct 12 2018 14:06:26.207
2018-10-12 14:06:28,371 INFO [main] encryption.MasterKeyServiceImpl
(MasterKeyServiceImpl.java:initializeFromFile(277)) - Loading from persistent
master: #1.0# Fri, Oct 12 2018 14:06:28.370{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24787) Cover with unit tests wizard step7 views
[ https://issues.apache.org/jira/browse/AMBARI-24787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16653783#comment-16653783 ] Hudson commented on AMBARI-24787: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #10225 (See [https://builds.apache.org/job/Ambari-trunk-Commit/10225/]) AMBARI-24787. Cover with unit tests wizard step7 views (akovalenko) (aleksandrkovalenko: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=e138e0eb23cdf9f55814659c28fb3aa83eb7f02d]) * (add) ambari-web/test/views/wizard/step7/databases_tab_view_test.js * (add) ambari-web/test/views/wizard/step7/directories_tab_view_test.js * (add) ambari-web/test/views/wizard/step7/credentials_tab_view_test.js * (edit) ambari-web/app/assets/test/tests.js * (add) ambari-web/test/views/wizard/step7/accounts_tab_view_test.js > Cover with unit tests wizard step7 views > > > Key: AMBARI-24787 > URL: https://issues.apache.org/jira/browse/AMBARI-24787 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24787) Cover with unit tests wizard step7 views
[ https://issues.apache.org/jira/browse/AMBARI-24787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-24787. -- Resolution: Fixed > Cover with unit tests wizard step7 views > > > Key: AMBARI-24787 > URL: https://issues.apache.org/jira/browse/AMBARI-24787 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24795) Allow skipping Python unit tests
[
https://issues.apache.org/jira/browse/AMBARI-24795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-24795:
---
Status: Patch Available (was: In Progress)
> Allow skipping Python unit tests
>
>
> Key: AMBARI-24795
> URL: https://issues.apache.org/jira/browse/AMBARI-24795
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-agent
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{ambari-server}} Python tests can be skipped by passing
> {{-DskipPythonTests}} to Maven. The goal of this task is to allow the same
> for {{ambari-agent}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24774) Wrong settings in exported blueprint
[
https://issues.apache.org/jira/browse/AMBARI-24774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16653716#comment-16653716
]
Hudson commented on AMBARI-24774:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #10224 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/10224/])
AMBARI-24774. Wrong settings in exported blueprint (#2475) (github:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=5a8af96159fe1fe43d2569d847a88de44dcf59c6])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/api/query/render/ClusterBlueprintRendererTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/api/query/render/ClusterBlueprintRenderer.java
> Wrong settings in exported blueprint
>
>
> Key: AMBARI-24774
> URL: https://issues.apache.org/jira/browse/AMBARI-24774
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Cluster blueprint export is broken wrt. the {{settings}} section.
> # Only one component per service is included.
> # Default setting value assumed to be {{false}}, ignoring component-level
> stack definition
> STR:
> # Disable "Auto Start" for Metrics Collector, for which it is enabled by
> default per stack definition
> # Enable "Auto Start" for both DataNode and NameNode
> # Export blueprint
> Result:
> {noformat:title=http://$AMBARI_SERVER:8080/api/v1/clusters/TEST?format=blueprint}
> "settings" : [
> {
> "recovery_settings" : [
> {
> "recovery_enabled" : "true"
> }
> ]
> },
> {
> "service_settings" : [
> {
> "recovery_enabled" : "true",
> "name" : "HDFS"
> }
> ]
> },
> {
> "component_settings" : [
> {
> "recovery_enabled" : "true",
> "name" : "NAMENODE"
> }
> ]
> }
> {noformat}
> Problem: creating a cluster using the exported blueprint results in different
> settings than the original cluster. "Auto Start" would be disabled for
> DataNode and enabled for Metrics Collector per stack defaults.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24795) Allow skipping Python unit tests
[
https://issues.apache.org/jira/browse/AMBARI-24795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24795:
Labels: pull-request-available (was: )
> Allow skipping Python unit tests
>
>
> Key: AMBARI-24795
> URL: https://issues.apache.org/jira/browse/AMBARI-24795
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-agent
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0
>
>
> {{ambari-server}} Python tests can be skipped by passing
> {{-DskipPythonTests}} to Maven. The goal of this task is to allow the same
> for {{ambari-agent}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24795) Allow skipping Python unit tests
Doroszlai, Attila created AMBARI-24795:
--
Summary: Allow skipping Python unit tests
Key: AMBARI-24795
URL: https://issues.apache.org/jira/browse/AMBARI-24795
Project: Ambari
Issue Type: Improvement
Components: ambari-agent
Reporter: Doroszlai, Attila
Assignee: Doroszlai, Attila
Fix For: 2.8.0
{{ambari-server}} Python tests can be skipped by passing {{-DskipPythonTests}}
to Maven. The goal of this task is to allow the same for {{ambari-agent}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24774) Wrong settings in exported blueprint
[
https://issues.apache.org/jira/browse/AMBARI-24774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila resolved AMBARI-24774.
Resolution: Fixed
> Wrong settings in exported blueprint
>
>
> Key: AMBARI-24774
> URL: https://issues.apache.org/jira/browse/AMBARI-24774
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Cluster blueprint export is broken wrt. the {{settings}} section.
> # Only one component per service is included.
> # Default setting value assumed to be {{false}}, ignoring component-level
> stack definition
> STR:
> # Disable "Auto Start" for Metrics Collector, for which it is enabled by
> default per stack definition
> # Enable "Auto Start" for both DataNode and NameNode
> # Export blueprint
> Result:
> {noformat:title=http://$AMBARI_SERVER:8080/api/v1/clusters/TEST?format=blueprint}
> "settings" : [
> {
> "recovery_settings" : [
> {
> "recovery_enabled" : "true"
> }
> ]
> },
> {
> "service_settings" : [
> {
> "recovery_enabled" : "true",
> "name" : "HDFS"
> }
> ]
> },
> {
> "component_settings" : [
> {
> "recovery_enabled" : "true",
> "name" : "NAMENODE"
> }
> ]
> }
> {noformat}
> Problem: creating a cluster using the exported blueprint results in different
> settings than the original cluster. "Auto Start" would be disabled for
> DataNode and enabled for Metrics Collector per stack defaults.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24741) Update simplejson to newest with speedup bindings to python2.7 and PyUnicodeUCS4/PyUnicodeUCS2 variations
[ https://issues.apache.org/jira/browse/AMBARI-24741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16653598#comment-16653598 ] Hudson commented on AMBARI-24741: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10223 (See [https://builds.apache.org/job/Ambari-trunk-Commit/10223/]) AMBARI-24741. Update simplejson to newest with speedup bindings to (github: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=bf9b58a9a5b3f81c8035b3aca17a2dba4a69bfe3]) * (edit) ambari-common/src/main/python/ambari_simplejson/README.txt * (add) ambari-common/src/main/python/ambari_simplejson/_speedups/posix/usc4/_speedups.so * (edit) ambari-common/src/main/python/ambari_simplejson/encoder.py * (add) ambari-common/src/main/python/ambari_simplejson/_speedups/win/_speedups.pyd * (add) ambari-common/src/main/python/ambari_simplejson/_speedups/ppc/__init__.py * (add) ambari-common/src/main/python/ambari_simplejson/c_extension.py * (add) ambari-common/src/main/python/ambari_simplejson/_speedups/posix/usc2/_speedups.so * (edit) ambari-agent/conf/unix/ambari-agent * (add) ambari-common/src/main/python/ambari_simplejson/_speedups/posix/__init__.py * (edit) ambari-common/src/main/python/ambari_simplejson/__init__.py * (add) ambari-common/src/main/python/ambari_simplejson/_speedups/posix/usc2/__init__.py * (delete) ambari-common/src/main/python/ambari_simplejson/_speedups.so * (add) ambari-common/src/main/python/ambari_simplejson/_speedups.c * (add) ambari-common/src/main/python/ambari_simplejson/_speedups/win/__init__.py * (add) ambari-common/src/main/python/ambari_simplejson/_speedups/ppc/_speedups.so * (add) ambari-common/src/main/python/ambari_simplejson/ordered_dict.py * (add) ambari-common/src/main/python/ambari_simplejson/_speedups/posix/usc4/__init__.py * (add) ambari-common/src/main/python/ambari_simplejson/errors.py * (edit) ambari-common/src/main/python/ambari_simplejson/decoder.py * (add) ambari-common/src/main/python/ambari_simplejson/raw_json.py * (add) ambari-common/src/main/python/ambari_simplejson/_speedups/__init__.py * (edit) ambari-common/src/main/python/resource_management/core/resources/jcepolicyinfo.py * (edit) ambari-common/src/main/python/ambari_simplejson/scanner.py * (edit) ambari-agent/src/main/python/ambari_agent/AmbariAgent.py * (add) ambari-common/src/main/python/ambari_simplejson/compat.py > Update simplejson to newest with speedup bindings to python2.7 and > PyUnicodeUCS4/PyUnicodeUCS2 variations > - > > Key: AMBARI-24741 > URL: https://issues.apache.org/jira/browse/AMBARI-24741 > Project: Ambari > Issue Type: Task > Components: ambari-agent, ambari-server >Affects Versions: 2.7.0 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 2h 50m > Remaining Estimate: 0h > > Current version of simlejson budled with Ambari doesn't provide performance > boost, as speedup lib is linked with libpython2.6, which caused slowness on > cluster deployments and increasing the overall CPU resource usage. > Simplejson need to be updated to support python 2.7, specially speedup > binding. As we supporting various distribs, we need to provide > PyUnicodeUCS4/PyUnicodeUCS2 lib variations as well. In the future we need > separate lib for ibm ppc > In addition, logging functionality should be added to agent, which will > notify if the boost is used. > The way how logging should be done: > on Agent start with message like: "Available boosts for: simplejson, > subproccess32" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24777) Infra Manager: Remove dependencies due to security concerns.
[ https://issues.apache.org/jira/browse/AMBARI-24777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16653577#comment-16653577 ] Hudson commented on AMBARI-24777: - SUCCESS: Integrated in Jenkins build Ambari-Infra-master-Commit #11 (See [https://builds.apache.org/job/Ambari-Infra-master-Commit/11/]) AMBARI-24777 - Infra Manager: Remove dependencies due to security (github: [https://gitbox.apache.org/repos/asf?p=ambari-infra.git&a=commit&h=47f9f7474582ee543aaa0d70bb3699634bc8a7ab]) * (edit) ambari-infra-manager/src/main/java/org/apache/ambari/infra/InfraManager.java * (edit) ambari-infra-manager/src/main/resources/swagger/swagger.html * (edit) ambari-infra-manager/src/main/java/org/apache/ambari/infra/conf/InfraManagerServletConfig.java * (edit) ambari-infra-manager/src/main/java/org/apache/ambari/infra/conf/InfraManagerJerseyResourceConfig.java * (add) ambari-infra-manager/src/main/java/org/apache/ambari/infra/conf/InfraManagerWebServerCustomizer.java * (edit) ambari-infra-manager-it/src/test/resources/stories/infra_api_tests.story * (edit) ambari-infra-manager/src/main/java/org/apache/ambari/infra/doc/InfraManagerApiDocStorage.java * (edit) ambari-infra-manager-it/src/test/java/org/apache/ambari/infra/steps/AbstractInfraSteps.java * (edit) ambari-infra-manager/src/main/java/org/apache/ambari/infra/rest/JobResource.java * (edit) ambari-infra-manager/src/main/resources/infra-manager-env.sh * (edit) pom.xml * (edit) ambari-infra-manager/pom.xml > Infra Manager: Remove dependencies due to security concerns. > > > Key: AMBARI-24777 > URL: https://issues.apache.org/jira/browse/AMBARI-24777 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 2.8.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24777) Infra Manager: Remove dependencies due to security concerns.
[
https://issues.apache.org/jira/browse/AMBARI-24777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16653560#comment-16653560
]
ASF GitHub Bot commented on AMBARI-24777:
-
kasakrisz closed pull request #7: AMBARI-24777 - Infra Manager: Remove
dependencies due to security concerns.
URL: https://github.com/apache/ambari-infra/pull/7
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git
a/ambari-infra-manager-it/src/test/java/org/apache/ambari/infra/steps/AbstractInfraSteps.java
b/ambari-infra-manager-it/src/test/java/org/apache/ambari/infra/steps/AbstractInfraSteps.java
index da962b9..24d603b 100644
---
a/ambari-infra-manager-it/src/test/java/org/apache/ambari/infra/steps/AbstractInfraSteps.java
+++
b/ambari-infra-manager-it/src/test/java/org/apache/ambari/infra/steps/AbstractInfraSteps.java
@@ -137,7 +137,6 @@ protected void addDocument(OffsetDateTime logtime) {
solrInputDocument.addField("level", "INFO");
solrInputDocument.addField("resource", "/ats/active");
solrInputDocument.addField("ip", "172.18.0.2");
-solrInputDocument.addField("evtTime", "2017-12-08T10:23:16.452Z");
solrInputDocument.addField("req_caller_id",
"HIVE_QUERY_ID:ambari-qa_20160317200111_223b3079-4a2d-431c-920f-6ba37ed63e9f");
solrInputDocument.addField("repoType", 1);
solrInputDocument.addField("enforcer", "hadoop-acl");
@@ -145,6 +144,7 @@ protected void addDocument(OffsetDateTime logtime) {
solrInputDocument.addField("message_md5", "-6778765776916226588");
solrInputDocument.addField("event_md5", "5627261521757462732");
solrInputDocument.addField("logtime", new
Date(logtime.toInstant().toEpochMilli()));
+solrInputDocument.addField("evtTime", new
Date(logtime.toInstant().toEpochMilli()));
solrInputDocument.addField("_ttl_", "+7DAYS");
solrInputDocument.addField("_expire_at_", "2017-12-15T10:23:19.106Z");
solr.add(solrInputDocument);
diff --git
a/ambari-infra-manager-it/src/test/resources/stories/infra_api_tests.story
b/ambari-infra-manager-it/src/test/resources/stories/infra_api_tests.story
index 729d609..2330474 100644
--- a/ambari-infra-manager-it/src/test/resources/stories/infra_api_tests.story
+++ b/ambari-infra-manager-it/src/test/resources/stories/infra_api_tests.story
@@ -44,7 +44,7 @@ Then solr does not contain documents between
2012-10-09T05:00:00.000Z and 2012-1
Scenario: Archiving documents to hdfs
Given 1000 documents in solr with logtime from 2014-01-04T05:00:00.000Z to
2014-01-06T20:00:00.000Z
-When start archive_audit_logs job with parameters
start=2014-01-04T05:00:00.000Z,end=2014-01-06T20:00:00.000Z,destination=HDFS
after 2 seconds
+When start archive_audit_logs job with parameters
start=2014-01-04T05:00:00.000Z,end=2014-01-06T20:00:00.000Z,destination=HDFS,hdfsDestinationDirectory=/test_audit_logs
after 2 seconds
Then Check 7 files exists on hdfs with filenames containing the text
audit_logs_-_2014-01-0 in the folder /test_audit_logs after 10 seconds
And solr does not contain documents between 2014-01-04T05:00:00.000Z and
2014-01-06T20:00:00.000Z after 10 seconds
diff --git a/ambari-infra-manager/pom.xml b/ambari-infra-manager/pom.xml
index f28f59d..3cd9860 100644
--- a/ambari-infra-manager/pom.xml
+++ b/ambari-infra-manager/pom.xml
@@ -30,15 +30,15 @@
ambari-infra-manager
-4.3.17.RELEASE
-4.2.4.RELEASE
-2.2.0.RELEASE
-2.25.1
+5.1.0.RELEASE
+5.1.0.RELEASE
+2.3.2.RELEASE
+2.27
9.4.11.v20180605
3.0.7.RELEASE
3.8.11.2
-2.0.2.RELEASE
-1.5.13.RELEASE
+3.0.10.RELEASE
+2.0.5.RELEASE
1.5.16
0.6.0
@@ -120,6 +120,11 @@
+
+ javax.validation
+ validation-api
+ 2.0.1.Final
+
junit
junit
@@ -194,26 +199,44 @@
org.springframework.boot
spring-boot-starter-web
${spring-boot.version}
+
+
+ org.springframework.boot
+ spring-boot-starter-tomcat
+
+
org.springframework.boot
- spring-boot-starter-security
+ spring-boot-starter-jetty
${spring-boot.version}
+
+
+ org.springframework.boot
+ spring-boot-starter-tomcat
+
+
org.springframework.boot
- spring-boot-starter-actuator
+ spring-boot-starter-security
${spring-boot.version}
org.springframework.boot
- spring-boot-starter-jetty
+ spring-boot-starter-actuator
${spring-boot.version}
org.springframework.boot
spring-boot-starter-jersey
${spring-boot.version}
+
+
+ org.springf
[jira] [Commented] (AMBARI-24777) Infra Manager: Remove dependencies due to security concerns.
[
https://issues.apache.org/jira/browse/AMBARI-24777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16653559#comment-16653559
]
ASF GitHub Bot commented on AMBARI-24777:
-
kasakrisz commented on a change in pull request #7: AMBARI-24777 - Infra
Manager: Remove dependencies due to security concerns.
URL: https://github.com/apache/ambari-infra/pull/7#discussion_r225932207
##
File path:
ambari-infra-manager-it/src/test/java/org/apache/ambari/infra/steps/AbstractInfraSteps.java
##
@@ -137,14 +137,14 @@ protected void addDocument(OffsetDateTime logtime) {
solrInputDocument.addField("level", "INFO");
solrInputDocument.addField("resource", "/ats/active");
solrInputDocument.addField("ip", "172.18.0.2");
-solrInputDocument.addField("evtTime", "2017-12-08T10:23:16.452Z");
solrInputDocument.addField("req_caller_id",
"HIVE_QUERY_ID:ambari-qa_20160317200111_223b3079-4a2d-431c-920f-6ba37ed63e9f");
solrInputDocument.addField("repoType", 1);
solrInputDocument.addField("enforcer", "hadoop-acl");
solrInputDocument.addField("cliType", "rpc");
solrInputDocument.addField("message_md5", "-6778765776916226588");
solrInputDocument.addField("event_md5", "5627261521757462732");
solrInputDocument.addField("logtime", new
Date(logtime.toInstant().toEpochMilli()));
+solrInputDocument.addField("evtTime", new
Date(logtime.toInstant().toEpochMilli()));
Review comment:
Yes, I changed the query text for `archive_audit_logs` to filter by
`evtTime` in another patch and forgot to run the integration tests. But that
patch is already merged.
When I run the tests after changing the versions of the dependencies the
tests didn't passed because `evtTime` was a constant.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Infra Manager: Remove dependencies due to security concerns.
>
>
> Key: AMBARI-24777
> URL: https://issues.apache.org/jira/browse/AMBARI-24777
> Project: Ambari
> Issue Type: Bug
> Components: ambari-infra
>Affects Versions: 2.8.0
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24777) Infra Manager: Remove dependencies due to security concerns.
[
https://issues.apache.org/jira/browse/AMBARI-24777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16653552#comment-16653552
]
ASF GitHub Bot commented on AMBARI-24777:
-
rlevas commented on a change in pull request #7: AMBARI-24777 - Infra Manager:
Remove dependencies due to security concerns.
URL: https://github.com/apache/ambari-infra/pull/7#discussion_r225927210
##
File path:
ambari-infra-manager-it/src/test/java/org/apache/ambari/infra/steps/AbstractInfraSteps.java
##
@@ -137,14 +137,14 @@ protected void addDocument(OffsetDateTime logtime) {
solrInputDocument.addField("level", "INFO");
solrInputDocument.addField("resource", "/ats/active");
solrInputDocument.addField("ip", "172.18.0.2");
-solrInputDocument.addField("evtTime", "2017-12-08T10:23:16.452Z");
solrInputDocument.addField("req_caller_id",
"HIVE_QUERY_ID:ambari-qa_20160317200111_223b3079-4a2d-431c-920f-6ba37ed63e9f");
solrInputDocument.addField("repoType", 1);
solrInputDocument.addField("enforcer", "hadoop-acl");
solrInputDocument.addField("cliType", "rpc");
solrInputDocument.addField("message_md5", "-6778765776916226588");
solrInputDocument.addField("event_md5", "5627261521757462732");
solrInputDocument.addField("logtime", new
Date(logtime.toInstant().toEpochMilli()));
+solrInputDocument.addField("evtTime", new
Date(logtime.toInstant().toEpochMilli()));
Review comment:
This seems out of place for this patch. Did you mean to add this line?
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Infra Manager: Remove dependencies due to security concerns.
>
>
> Key: AMBARI-24777
> URL: https://issues.apache.org/jira/browse/AMBARI-24777
> Project: Ambari
> Issue Type: Bug
> Components: ambari-infra
>Affects Versions: 2.8.0
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24794) Adding Ranger Password configs in Admin Settings section under Advanced config
[ https://issues.apache.org/jira/browse/AMBARI-24794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-24794: - Attachment: AMBARI-24794.patch > Adding Ranger Password configs in Admin Settings section under Advanced config > -- > > Key: AMBARI-24794 > URL: https://issues.apache.org/jira/browse/AMBARI-24794 > Project: Ambari > Issue Type: Bug >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Major > Labels: pull-request-available > Attachments: AMBARI-24794.patch > > Time Spent: 10m > Remaining Estimate: 0h > > This jira is fixing the below password configs to be shown in 'Admin > Settings' section under Advanced Config section for Ranger service. > * rangerusersync_user_password > * rangertagsync_user_password > * keyadmin_user_password -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24794) Adding Ranger Password configs in Admin Settings section under Advanced config
[ https://issues.apache.org/jira/browse/AMBARI-24794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-24794: - Status: Patch Available (was: In Progress) > Adding Ranger Password configs in Admin Settings section under Advanced config > -- > > Key: AMBARI-24794 > URL: https://issues.apache.org/jira/browse/AMBARI-24794 > Project: Ambari > Issue Type: Bug >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Major > Labels: pull-request-available > Attachments: AMBARI-24794.patch > > Time Spent: 10m > Remaining Estimate: 0h > > This jira is fixing the below password configs to be shown in 'Admin > Settings' section under Advanced Config section for Ranger service. > * rangerusersync_user_password > * rangertagsync_user_password > * keyadmin_user_password -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24794) Adding Ranger Password configs in Admin Settings section under Advanced config
[ https://issues.apache.org/jira/browse/AMBARI-24794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24794: Labels: pull-request-available (was: ) > Adding Ranger Password configs in Admin Settings section under Advanced config > -- > > Key: AMBARI-24794 > URL: https://issues.apache.org/jira/browse/AMBARI-24794 > Project: Ambari > Issue Type: Bug >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Major > Labels: pull-request-available > > This jira is fixing the below password configs to be shown in 'Admin > Settings' section under Advanced Config section for Ranger service. > * rangerusersync_user_password > * rangertagsync_user_password > * keyadmin_user_password -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24794) Adding Ranger Password configs in Admin Settings section under Advanced config
Mugdha Varadkar created AMBARI-24794: Summary: Adding Ranger Password configs in Admin Settings section under Advanced config Key: AMBARI-24794 URL: https://issues.apache.org/jira/browse/AMBARI-24794 Project: Ambari Issue Type: Bug Reporter: Mugdha Varadkar Assignee: Mugdha Varadkar This jira is fixing the below password configs to be shown in 'Admin Settings' section under Advanced Config section for Ranger service. * rangerusersync_user_password * rangertagsync_user_password * keyadmin_user_password -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24777) Infra Manager: Remove dependencies due to security concerns.
[ https://issues.apache.org/jira/browse/AMBARI-24777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16653466#comment-16653466 ] ASF GitHub Bot commented on AMBARI-24777: - kasakrisz commented on a change in pull request #7: AMBARI-24777 - Infra Manager: Remove dependencies due to security concerns. URL: https://github.com/apache/ambari-infra/pull/7#discussion_r225909824 ## File path: ambari-infra-manager/pom.xml ## @@ -400,7 +439,7 @@ org.webjars swagger-ui - 2.2.2 + 3.19.0 Review comment: I added a commit which replace the swagger.html to the new version. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Infra Manager: Remove dependencies due to security concerns. > > > Key: AMBARI-24777 > URL: https://issues.apache.org/jira/browse/AMBARI-24777 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 2.8.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24777) Infra Manager: Remove dependencies due to security concerns.
[ https://issues.apache.org/jira/browse/AMBARI-24777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16653462#comment-16653462 ] ASF GitHub Bot commented on AMBARI-24777: - asfgit commented on issue #7: AMBARI-24777 - Infra Manager: Remove dependencies due to security concerns. URL: https://github.com/apache/ambari-infra/pull/7#issuecomment-430611309 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/Ambari-Infra-Github-PR-Builder/11/ Test PASSed. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Infra Manager: Remove dependencies due to security concerns. > > > Key: AMBARI-24777 > URL: https://issues.apache.org/jira/browse/AMBARI-24777 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 2.8.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24775) Configuration warning: insert a space char between label value and unit-name
[
https://issues.apache.org/jira/browse/AMBARI-24775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16653396#comment-16653396
]
Hudson commented on AMBARI-24775:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #10222 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/10222/])
AMBARI-24775 - Configuration warning: insert a space char between label
(github:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=78bd9ccd523af5ba2a7f1f9b4b00e578c46c69a3])
* (edit)
ambari-web/test/views/common/configs/widgets/slider_config_widget_view_test.js
* (edit)
ambari-web/app/views/common/configs/widgets/slider_config_widget_view.js
> Configuration warning: insert a space char between label value and unit-name
>
>
> Key: AMBARI-24775
> URL: https://issues.apache.org/jira/browse/AMBARI-24775
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.8.0
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> On Ambari enhanced UI configuration and Configuration warning page inserting
> a space character between label value and unit-name when it is shown as a
> warning tooltip and text.
> from
> {code}
> 2days
> 100GB
> {code}
> to
> {code}
> 2 days
> 100 GB
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24793) Background tasks dialog should indicate the Request User
[ https://issues.apache.org/jira/browse/AMBARI-24793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bjorn Olsen updated AMBARI-24793: - Summary: Background tasks dialog should indicate the Request User (was: Background tasks dialog should show the Request User) > Background tasks dialog should indicate the Request User > > > Key: AMBARI-24793 > URL: https://issues.apache.org/jira/browse/AMBARI-24793 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Reporter: Bjorn Olsen >Priority: Minor > > In a multi-user environment it is useful to know which user has initiated a > particular administrative function. This assists when support is carried out > by multiple users who may need to ascertain from other users why a particular > action was done. > Currently this is easily visible for configuration changes, but not for > starting/stopping services, running service checks etc. > > This improvement is to add the "Requesting user" to the current "Background > tasks" dialog so that it is immediately apparent which user requested each > action. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24793) Background tasks dialog should indicate the user which requested the task
[ https://issues.apache.org/jira/browse/AMBARI-24793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bjorn Olsen updated AMBARI-24793: - Summary: Background tasks dialog should indicate the user which requested the task (was: Background tasks dialog should indicate the Request User) > Background tasks dialog should indicate the user which requested the task > - > > Key: AMBARI-24793 > URL: https://issues.apache.org/jira/browse/AMBARI-24793 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Reporter: Bjorn Olsen >Priority: Minor > > In a multi-user environment it is useful to know which user has initiated a > particular administrative function. This assists when support is carried out > by multiple users who may need to ascertain from other users why a particular > action was done. > Currently this is easily visible for configuration changes, but not for > starting/stopping services, running service checks etc. > > This improvement is to add the "Requesting user" to the current "Background > tasks" dialog so that it is immediately apparent which user requested each > action. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24793) Background tasks dialog should show the User
Bjorn Olsen created AMBARI-24793: Summary: Background tasks dialog should show the User Key: AMBARI-24793 URL: https://issues.apache.org/jira/browse/AMBARI-24793 Project: Ambari Issue Type: Improvement Components: ambari-server Reporter: Bjorn Olsen In a multi-user environment it is useful to know which user has initiated a particular administrative function. This assists when support is carried out by multiple users who may need to ascertain from other users why a particular action was done. Currently this is easily visible for configuration changes, but not for starting/stopping services, running service checks etc. This improvement is to add the "Requesting user" to the current "Background tasks" dialog so that it is immediately apparent which user requested each action. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24793) Background tasks dialog should show the Request User
[ https://issues.apache.org/jira/browse/AMBARI-24793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bjorn Olsen updated AMBARI-24793: - Summary: Background tasks dialog should show the Request User (was: Background tasks dialog should show the User) > Background tasks dialog should show the Request User > > > Key: AMBARI-24793 > URL: https://issues.apache.org/jira/browse/AMBARI-24793 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Reporter: Bjorn Olsen >Priority: Minor > > In a multi-user environment it is useful to know which user has initiated a > particular administrative function. This assists when support is carried out > by multiple users who may need to ascertain from other users why a particular > action was done. > Currently this is easily visible for configuration changes, but not for > starting/stopping services, running service checks etc. > > This improvement is to add the "Requesting user" to the current "Background > tasks" dialog so that it is immediately apparent which user requested each > action. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24777) Infra Manager: Remove dependencies due to security concerns.
[ https://issues.apache.org/jira/browse/AMBARI-24777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16653337#comment-16653337 ] ASF GitHub Bot commented on AMBARI-24777: - oleewere commented on a change in pull request #7: AMBARI-24777 - Infra Manager: Remove dependencies due to security concerns. URL: https://github.com/apache/ambari-infra/pull/7#discussion_r225869705 ## File path: ambari-infra-manager/pom.xml ## @@ -400,7 +439,7 @@ org.webjars swagger-ui - 2.2.2 + 3.19.0 Review comment: it worth a re-check how is that working with our swagger.html, as it should not have references to 2.2.2 js files anymore. maybe browser just cached those files etc. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Infra Manager: Remove dependencies due to security concerns. > > > Key: AMBARI-24777 > URL: https://issues.apache.org/jira/browse/AMBARI-24777 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 2.8.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24787) Cover with unit tests wizard step7 views
[ https://issues.apache.org/jira/browse/AMBARI-24787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24787: Labels: pull-request-available (was: ) > Cover with unit tests wizard step7 views > > > Key: AMBARI-24787 > URL: https://issues.apache.org/jira/browse/AMBARI-24787 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24741) Update simplejson to newest with speedup bindings to python2.7 and PyUnicodeUCS4/PyUnicodeUCS2 variations
[ https://issues.apache.org/jira/browse/AMBARI-24741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-24741: - Status: Patch Available (was: In Progress) > Update simplejson to newest with speedup bindings to python2.7 and > PyUnicodeUCS4/PyUnicodeUCS2 variations > - > > Key: AMBARI-24741 > URL: https://issues.apache.org/jira/browse/AMBARI-24741 > Project: Ambari > Issue Type: Task > Components: ambari-agent, ambari-server >Affects Versions: 2.7.0 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Current version of simlejson budled with Ambari doesn't provide performance > boost, as speedup lib is linked with libpython2.6, which caused slowness on > cluster deployments and increasing the overall CPU resource usage. > Simplejson need to be updated to support python 2.7, specially speedup > binding. As we supporting various distribs, we need to provide > PyUnicodeUCS4/PyUnicodeUCS2 lib variations as well. In the future we need > separate lib for ibm ppc > In addition, logging functionality should be added to agent, which will > notify if the boost is used. > The way how logging should be done: > on Agent start with message like: "Available boosts for: simplejson, > subproccess32" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24792) Infra Manager: not all the documents archived
Krisztian Kasa created AMBARI-24792: --- Summary: Infra Manager: not all the documents archived Key: AMBARI-24792 URL: https://issues.apache.org/jira/browse/AMBARI-24792 Project: Ambari Issue Type: Bug Components: ambari-infra Affects Versions: 2.8.0 Reporter: Krisztian Kasa Assignee: Krisztian Kasa Fix For: 2.8.0 Infra manager does not use the sort_column properties when reading the documents to archive. This leads to some of the documents are not exported. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24761) Infra Manager: hive support for archiving Infra Solr
[ https://issues.apache.org/jira/browse/AMBARI-24761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krisztian Kasa updated AMBARI-24761: Resolution: Fixed Status: Resolved (was: Patch Available) > Infra Manager: hive support for archiving Infra Solr > > > Key: AMBARI-24761 > URL: https://issues.apache.org/jira/browse/AMBARI-24761 > Project: Ambari > Issue Type: Bug > Components: infra >Affects Versions: 2.8.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > > When exporting Solr documents from logsearch and ranger collections save it > to a format which can be parsed by Hive. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24741) Update simplejson to newest with speedup bindings to python2.7 and PyUnicodeUCS4/PyUnicodeUCS2 variations
[ https://issues.apache.org/jira/browse/AMBARI-24741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24741: Labels: pull-request-available (was: ) > Update simplejson to newest with speedup bindings to python2.7 and > PyUnicodeUCS4/PyUnicodeUCS2 variations > - > > Key: AMBARI-24741 > URL: https://issues.apache.org/jira/browse/AMBARI-24741 > Project: Ambari > Issue Type: Task > Components: ambari-agent, ambari-server >Affects Versions: 2.7.0 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Labels: pull-request-available > Fix For: 2.8.0 > > > Current version of simlejson budled with Ambari doesn't provide performance > boost, as speedup lib is linked with libpython2.6, which caused slowness on > cluster deployments and increasing the overall CPU resource usage. > Simplejson need to be updated to support python 2.7, specially speedup > binding. As we supporting various distribs, we need to provide > PyUnicodeUCS4/PyUnicodeUCS2 lib variations as well. In the future we need > separate lib for ibm ppc > In addition, logging functionality should be added to agent, which will > notify if the boost is used. > The way how logging should be done: > on Agent start with message like: "Available boosts for: simplejson, > subproccess32" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24777) Infra Manager: Remove dependencies due to security concerns.
[ https://issues.apache.org/jira/browse/AMBARI-24777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krisztian Kasa updated AMBARI-24777: Status: Patch Available (was: Open) > Infra Manager: Remove dependencies due to security concerns. > > > Key: AMBARI-24777 > URL: https://issues.apache.org/jira/browse/AMBARI-24777 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 2.8.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
