[jira] [Resolved] (FALCON-2341) Entity SLA Alert publishing wrong results into DB
[ https://issues.apache.org/jira/browse/FALCON-2341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao resolved FALCON-2341. - Resolution: Fixed > Entity SLA Alert publishing wrong results into DB > - > > Key: FALCON-2341 > URL: https://issues.apache.org/jira/browse/FALCON-2341 > Project: Falcon > Issue Type: Bug > Components: metrics >Reporter: Amit Khanna >Assignee: Amit Khanna >Priority: Major > Fix For: trunk > > > Issues with current system - > 1) For process SLA Alert ENTITY_SLA_ALERTS table is getting flooded with same > entries. > 2) For feed no entry is going into ENTITY_SLA_ALERTS table. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FALCON-2341) Entity SLA Alert publishing wrong results into DB
[ https://issues.apache.org/jira/browse/FALCON-2341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao reassigned FALCON-2341: --- Assignee: Amit Khanna > Entity SLA Alert publishing wrong results into DB > - > > Key: FALCON-2341 > URL: https://issues.apache.org/jira/browse/FALCON-2341 > Project: Falcon > Issue Type: Bug > Components: metrics >Reporter: Amit Khanna >Assignee: Amit Khanna >Priority: Major > Fix For: trunk > > > Issues with current system - > 1) For process SLA Alert ENTITY_SLA_ALERTS table is getting flooded with same > entries. > 2) For feed no entry is going into ENTITY_SLA_ALERTS table. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FALCON-2341) Entity SLA Alert publishing wrong results into DB
[ https://issues.apache.org/jira/browse/FALCON-2341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-2341: Fix Version/s: trunk > Entity SLA Alert publishing wrong results into DB > - > > Key: FALCON-2341 > URL: https://issues.apache.org/jira/browse/FALCON-2341 > Project: Falcon > Issue Type: Bug > Components: metrics >Reporter: Amit Khanna >Priority: Major > Fix For: trunk > > > Issues with current system - > 1) For process SLA Alert ENTITY_SLA_ALERTS table is getting flooded with same > entries. > 2) For feed no entry is going into ENTITY_SLA_ALERTS table. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FALCON-2340) Passing groupid to oozie while scheduling the process
[ https://issues.apache.org/jira/browse/FALCON-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-2340: Fix Version/s: trunk > Passing groupid to oozie while scheduling the process > - > > Key: FALCON-2340 > URL: https://issues.apache.org/jira/browse/FALCON-2340 > Project: Falcon > Issue Type: Task >Reporter: Narayan Periwal >Assignee: Narayan Periwal >Priority: Minor > Fix For: trunk > > > Currently, falcon does not pass the group information to oozie. > This need to be passed so that any member of the group can perform allowed > actions on workflow engine jobs -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (FALCON-2340) Passing groupid to oozie while scheduling the process
[ https://issues.apache.org/jira/browse/FALCON-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao resolved FALCON-2340. - Resolution: Fixed > Passing groupid to oozie while scheduling the process > - > > Key: FALCON-2340 > URL: https://issues.apache.org/jira/browse/FALCON-2340 > Project: Falcon > Issue Type: Task >Reporter: Narayan Periwal >Assignee: Narayan Periwal >Priority: Minor > Fix For: trunk > > > Currently, falcon does not pass the group information to oozie. > This need to be passed so that any member of the group can perform allowed > actions on workflow engine jobs -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (FALCON-2339) Falcon doesn't work with sql server as database
[
https://issues.apache.org/jira/browse/FALCON-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pallavi Rao resolved FALCON-2339.
-
Resolution: Fixed
> Falcon doesn't work with sql server as database
> ---
>
> Key: FALCON-2339
> URL: https://issues.apache.org/jira/browse/FALCON-2339
> Project: Falcon
> Issue Type: Bug
> Components: common
>Affects Versions: 0.9
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
>Priority: Major
> Fix For: trunk
>
>
> Despite using JDBC to connect to database, trying to use sqlserver results in
> an error:
>
> {noformat}
> 2018-05-25 07:37:07,981 ERROR - [main:] ~ Failed startup of context
> org.mortbay.jetty.webapp.WebAppContext@304b9f1a{/,/usr/local/lib/falcon/server/webapp/falcon}
> (log:87)
> java.lang.RuntimeException: org.apache.falcon.FalconException:
> javax.persistence.PersistenceException: No persistence providers available
> for "falcon-sqlserver" after trying the following discovered implementations:
> org.apache.openjpa.persistence.PersistenceProviderImpl
> at
> org.apache.falcon.listener.ContextStartupListener.contextInitialized(ContextStartupListener.java:59)
> at
> org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:549)
> at org.mortbay.jetty.servlet.Context.startContext(Context.java:136)
> at
> org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1282)
> at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:518)
> at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:499)
> at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
> at org.mortbay.jetty.Server.doStart(Server.java:224)
> at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at org.apache.falcon.util.EmbeddedServer.start(EmbeddedServer.java:58)
> at org.apache.falcon.FalconServer.main(FalconServer.java:120)
> Caused by: org.apache.falcon.FalconException:
> javax.persistence.PersistenceException: No persistence providers available
> for "falcon-sqlserver" after trying the following discovered implementations:
> org.apache.openjpa.persistence.PersistenceProviderImpl
> at
> org.apache.falcon.service.ServiceInitializer.initialize(ServiceInitializer.java:50)
> at
> org.apache.falcon.listener.ContextStartupListener.contextInitialized(ContextStartupListener.java:56)
> ... 11 more
> Caused by: javax.persistence.PersistenceException: No persistence providers
> available for "falcon-sqlserver" after trying the following discovered
> implementations: org.apache.openjpa.persistence.PersistenceProviderImpl
> at
> javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:182)
> at org.apache.falcon.service.FalconJPAService.init(FalconJPAService.java:89)
> at
> org.apache.falcon.service.ServiceInitializer.initialize(ServiceInitializer.java:47)
> ... 12 more
> {noformat}
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (FALCON-2339) Falcon doesn't work with sql server as database
[
https://issues.apache.org/jira/browse/FALCON-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pallavi Rao updated FALCON-2339:
Fix Version/s: trunk
> Falcon doesn't work with sql server as database
> ---
>
> Key: FALCON-2339
> URL: https://issues.apache.org/jira/browse/FALCON-2339
> Project: Falcon
> Issue Type: Bug
> Components: common
>Affects Versions: 0.9
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
>Priority: Major
> Fix For: trunk
>
>
> Despite using JDBC to connect to database, trying to use sqlserver results in
> an error:
>
> {noformat}
> 2018-05-25 07:37:07,981 ERROR - [main:] ~ Failed startup of context
> org.mortbay.jetty.webapp.WebAppContext@304b9f1a{/,/usr/local/lib/falcon/server/webapp/falcon}
> (log:87)
> java.lang.RuntimeException: org.apache.falcon.FalconException:
> javax.persistence.PersistenceException: No persistence providers available
> for "falcon-sqlserver" after trying the following discovered implementations:
> org.apache.openjpa.persistence.PersistenceProviderImpl
> at
> org.apache.falcon.listener.ContextStartupListener.contextInitialized(ContextStartupListener.java:59)
> at
> org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:549)
> at org.mortbay.jetty.servlet.Context.startContext(Context.java:136)
> at
> org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1282)
> at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:518)
> at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:499)
> at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
> at org.mortbay.jetty.Server.doStart(Server.java:224)
> at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at org.apache.falcon.util.EmbeddedServer.start(EmbeddedServer.java:58)
> at org.apache.falcon.FalconServer.main(FalconServer.java:120)
> Caused by: org.apache.falcon.FalconException:
> javax.persistence.PersistenceException: No persistence providers available
> for "falcon-sqlserver" after trying the following discovered implementations:
> org.apache.openjpa.persistence.PersistenceProviderImpl
> at
> org.apache.falcon.service.ServiceInitializer.initialize(ServiceInitializer.java:50)
> at
> org.apache.falcon.listener.ContextStartupListener.contextInitialized(ContextStartupListener.java:56)
> ... 11 more
> Caused by: javax.persistence.PersistenceException: No persistence providers
> available for "falcon-sqlserver" after trying the following discovered
> implementations: org.apache.openjpa.persistence.PersistenceProviderImpl
> at
> javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:182)
> at org.apache.falcon.service.FalconJPAService.init(FalconJPAService.java:89)
> at
> org.apache.falcon.service.ServiceInitializer.initialize(ServiceInitializer.java:47)
> ... 12 more
> {noformat}
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (FALCON-2336) StartupProperties shouldn't have specific logic to handle safemode property.
[ https://issues.apache.org/jira/browse/FALCON-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao resolved FALCON-2336. - Resolution: Fixed Fix Version/s: trunk Issue resolved by pull request 410 [https://github.com/apache/falcon/pull/410] > StartupProperties shouldn't have specific logic to handle safemode property. > > > Key: FALCON-2336 > URL: https://issues.apache.org/jira/browse/FALCON-2336 > Project: Falcon > Issue Type: Improvement >Reporter: Pallavi Rao >Assignee: Pallavi Rao >Priority: Minor > Fix For: trunk > > > Two problems with that: > # Violation of class responsibility - Falcon Server is already handling the > safemode prop and any related code should be there. > # If Hadoop is secure, the server won't start without an explicit kinit > before server start as server won't have credentials to talk to Hadoop yet. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (FALCON-2335) Entity update should not lock the cluster entity
[ https://issues.apache.org/jira/browse/FALCON-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao resolved FALCON-2335. - Resolution: Fixed > Entity update should not lock the cluster entity > > > Key: FALCON-2335 > URL: https://issues.apache.org/jira/browse/FALCON-2335 > Project: Falcon > Issue Type: Improvement >Reporter: Pallavi Rao >Assignee: Pallavi Rao >Priority: Minor > > Multiple entities (feeds/processes) belonging to a cluster cannot be updated > simultaneously, as a cluster lock is obtained during update. This lock is > unnecessary, unless the cluster itself is being update. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (FALCON-1691) Falcon 0.9 release
[ https://issues.apache.org/jira/browse/FALCON-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao resolved FALCON-1691. - Resolution: Fixed Fix Version/s: (was: 0.10) 0.9 > Falcon 0.9 release > -- > > Key: FALCON-1691 > URL: https://issues.apache.org/jira/browse/FALCON-1691 > Project: Falcon > Issue Type: Task >Reporter: Pallavi Rao >Assignee: Pallavi Rao >Priority: Major > Fix For: 0.9 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FALCON-2336) StartupProperties shouldn't have specific logic to handle safemode property.
[ https://issues.apache.org/jira/browse/FALCON-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao reassigned FALCON-2336: --- Assignee: Pallavi Rao > StartupProperties shouldn't have specific logic to handle safemode property. > > > Key: FALCON-2336 > URL: https://issues.apache.org/jira/browse/FALCON-2336 > Project: Falcon > Issue Type: Improvement >Reporter: Pallavi Rao >Assignee: Pallavi Rao >Priority: Minor > > Two problems with that: > # Violation of class responsibility - Falcon Server is already handling the > safemode prop and any related code should be there. > # If Hadoop is secure, the server won't start without an explicit kinit > before server start as server won't have credentials to talk to Hadoop yet. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FALCON-2336) StartupProperties shouldn't have specific logic to handle safemode property.
Pallavi Rao created FALCON-2336: --- Summary: StartupProperties shouldn't have specific logic to handle safemode property. Key: FALCON-2336 URL: https://issues.apache.org/jira/browse/FALCON-2336 Project: Falcon Issue Type: Improvement Reporter: Pallavi Rao Two problems with that: # Violation of class responsibility - Falcon Server is already handling the safemode prop and any related code should be there. # If Hadoop is secure, the server won't start without an explicit kinit before server start as server won't have credentials to talk to Hadoop yet. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (FALCON-2309) Create Release Notes
[ https://issues.apache.org/jira/browse/FALCON-2309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao resolved FALCON-2309. - Resolution: Fixed > Create Release Notes > > > Key: FALCON-2309 > URL: https://issues.apache.org/jira/browse/FALCON-2309 > Project: Falcon > Issue Type: Sub-task >Reporter: Pallavi Rao >Assignee: Pallavi Rao >Priority: Major > Fix For: 0.11 > > Attachments: RelaseNotes-ApacheFalcon-0.11.docx, > RelaseNotes-ApacheFalcon-0.11.pdf > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FALCON-2335) Entity update should not lock the cluster entity
[ https://issues.apache.org/jira/browse/FALCON-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao reassigned FALCON-2335: --- Assignee: Pallavi Rao > Entity update should not lock the cluster entity > > > Key: FALCON-2335 > URL: https://issues.apache.org/jira/browse/FALCON-2335 > Project: Falcon > Issue Type: Improvement >Reporter: Pallavi Rao >Assignee: Pallavi Rao >Priority: Minor > > Multiple entities (feeds/processes) belonging to a cluster cannot be updated > simultaneously, as a cluster lock is obtained during update. This lock is > unnecessary, unless the cluster itself is being update. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FALCON-2333) falcon replication: success file filter in not getting honoured in replication jobs with hadoop 2.8.0 and above
[ https://issues.apache.org/jira/browse/FALCON-2333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao reassigned FALCON-2333: --- Assignee: Raghavendra Singh > falcon replication: success file filter in not getting honoured in > replication jobs with hadoop 2.8.0 and above > --- > > Key: FALCON-2333 > URL: https://issues.apache.org/jira/browse/FALCON-2333 > Project: Falcon > Issue Type: Bug > Components: replication >Affects Versions: 0.11 >Reporter: Raghavendra Singh >Assignee: Raghavendra Singh >Priority: Major > Fix For: trunk > > > After the changes done in > https://issues.apache.org/jira/browse/HADOOP-1540 > The FilteredCopyListing override is not overriding the shouldCopy function, > hence the availability flag filter is not getting applied -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (FALCON-2333) falcon replication: success file filter in not getting honoured in replication jobs with hadoop 2.8.0 and above
[ https://issues.apache.org/jira/browse/FALCON-2333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao resolved FALCON-2333. - Resolution: Fixed Fix Version/s: trunk Issue resolved by pull request 407 [https://github.com/apache/falcon/pull/407] > falcon replication: success file filter in not getting honoured in > replication jobs with hadoop 2.8.0 and above > --- > > Key: FALCON-2333 > URL: https://issues.apache.org/jira/browse/FALCON-2333 > Project: Falcon > Issue Type: Bug > Components: replication >Affects Versions: 0.11 >Reporter: Raghavendra Singh >Priority: Major > Fix For: trunk > > > After the changes done in > https://issues.apache.org/jira/browse/HADOOP-1540 > The FilteredCopyListing override is not overriding the shouldCopy function, > hence the availability flag filter is not getting applied -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FALCON-2335) Entity update should not lock the cluster entity
Pallavi Rao created FALCON-2335: --- Summary: Entity update should not lock the cluster entity Key: FALCON-2335 URL: https://issues.apache.org/jira/browse/FALCON-2335 Project: Falcon Issue Type: Improvement Reporter: Pallavi Rao Multiple entities (feeds/processes) belonging to a cluster cannot be updated simultaneously, as a cluster lock is obtained during update. This lock is unnecessary, unless the cluster itself is being update. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (FALCON-2328) Upgrade PR merge script to Python3
[
https://issues.apache.org/jira/browse/FALCON-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pallavi Rao resolved FALCON-2328.
-
Resolution: Fixed
Fix Version/s: trunk
Issue resolved by pull request 404
[https://github.com/apache/falcon/pull/404]
> Upgrade PR merge script to Python3
> --
>
> Key: FALCON-2328
> URL: https://issues.apache.org/jira/browse/FALCON-2328
> Project: Falcon
> Issue Type: Improvement
>Reporter: Pallavi Rao
>Assignee: Pallavi Rao
>Priority: Major
> Fix For: trunk
>
>
> python2 uses an older version of openssl and this is causing the following
> error:
> {noformat}
> urllib2.URLError: alert protocol version (_ssl.c:590)>{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (FALCON-2327) Upgrade Hadoop version of Falcon to 2.7
[ https://issues.apache.org/jira/browse/FALCON-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao resolved FALCON-2327. - Resolution: Fixed Fix Version/s: trunk Issue resolved by pull request 403 [https://github.com/apache/falcon/pull/403] > Upgrade Hadoop version of Falcon to 2.7 > --- > > Key: FALCON-2327 > URL: https://issues.apache.org/jira/browse/FALCON-2327 > Project: Falcon > Issue Type: Bug >Reporter: Pallavi Rao >Assignee: Pallavi Rao >Priority: Major > Fix For: trunk > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (FALCON-2330) Update Notice copyright period to 2018
[ https://issues.apache.org/jira/browse/FALCON-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao resolved FALCON-2330. - Resolution: Fixed > Update Notice copyright period to 2018 > -- > > Key: FALCON-2330 > URL: https://issues.apache.org/jira/browse/FALCON-2330 > Project: Falcon > Issue Type: Bug >Reporter: sandeep samudrala >Assignee: sandeep samudrala >Priority: Major > > Update Notice copyright period to 2018 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FALCON-2328) Upgrade PR merge script to Python3
Pallavi Rao created FALCON-2328:
---
Summary: Upgrade PR merge script to Python3
Key: FALCON-2328
URL: https://issues.apache.org/jira/browse/FALCON-2328
Project: Falcon
Issue Type: Improvement
Reporter: Pallavi Rao
Assignee: Pallavi Rao
python2 uses an older version of openssl and this is causing the following
error:
{noformat}
urllib2.URLError: {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (FALCON-2326) Falcon Pull Request Builds failing
[ https://issues.apache.org/jira/browse/FALCON-2326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao resolved FALCON-2326. - Resolution: Fixed > Falcon Pull Request Builds failing > -- > > Key: FALCON-2326 > URL: https://issues.apache.org/jira/browse/FALCON-2326 > Project: Falcon > Issue Type: Bug >Reporter: Pallavi Rao >Assignee: Pallavi Rao >Priority: Major > > Details -> https://builds.apache.org/job/Apache-Falcon-Pull-Request-Build/924 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FALCON-2327) Upgrade Hadoop version of Falcon to 2.7
Pallavi Rao created FALCON-2327: --- Summary: Upgrade Hadoop version of Falcon to 2.7 Key: FALCON-2327 URL: https://issues.apache.org/jira/browse/FALCON-2327 Project: Falcon Issue Type: Bug Reporter: Pallavi Rao Assignee: Pallavi Rao -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FALCON-2326) Falcon Pull Request Builds failing
Pallavi Rao created FALCON-2326: --- Summary: Falcon Pull Request Builds failing Key: FALCON-2326 URL: https://issues.apache.org/jira/browse/FALCON-2326 Project: Falcon Issue Type: Bug Reporter: Pallavi Rao Assignee: Pallavi Rao Details -> https://builds.apache.org/job/Apache-Falcon-Pull-Request-Build/924 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (FALCON-2314) Bump TestNG version to 6.13.1 to avoid BeanShell dependency
[ https://issues.apache.org/jira/browse/FALCON-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao resolved FALCON-2314. - Resolution: Fixed > Bump TestNG version to 6.13.1 to avoid BeanShell dependency > --- > > Key: FALCON-2314 > URL: https://issues.apache.org/jira/browse/FALCON-2314 > Project: Falcon > Issue Type: Bug > Components: client, tests >Affects Versions: 0.10 >Reporter: Denes Bodo >Assignee: Denes Bodo >Priority: Major > Attachments: FALCON-2314_001.patch > > > In our environment we needed to get rid of LGPL BeanShell TestNG dependency. > In this case > EvictedInstanceSerDeTest.testDeserializeEvictedInstancePathsForNoEviction is > failing. The reason of the fail is the newer TestNG runs the two Serialize > method first, then runs the two Deserialize next. This means > testDeserializeEvictedInstancePathsForNoEviction which tests for empty files > found a file with unexpected content and fails. > I suggest splitting the two files into different ones as first attached patch > shows. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (FALCON-2321) When Prism is Kerberized, it doesn't pass its token while making calls to Falcon Server
[ https://issues.apache.org/jira/browse/FALCON-2321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao resolved FALCON-2321. - Resolution: Fixed > When Prism is Kerberized, it doesn't pass its token while making calls to > Falcon Server > --- > > Key: FALCON-2321 > URL: https://issues.apache.org/jira/browse/FALCON-2321 > Project: Falcon > Issue Type: Bug >Reporter: Pallavi Rao >Assignee: Pallavi Rao >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (FALCON-2318) Unit tests in JMSMessageConsumerTest are failing when running multiple times without clean
[ https://issues.apache.org/jira/browse/FALCON-2318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao resolved FALCON-2318. - Resolution: Fixed > Unit tests in JMSMessageConsumerTest are failing when running multiple times > without clean > -- > > Key: FALCON-2318 > URL: https://issues.apache.org/jira/browse/FALCON-2318 > Project: Falcon > Issue Type: Bug > Components: messaging, tests >Affects Versions: 0.10 >Reporter: Denes Bodo >Assignee: Denes Bodo >Priority: Minor > > When I run mvn test or from Idea for the first time, tests in > JMSMessageConsumerTest are passing. When I rerun the tests without mvn clean > or deleting /messaging/target/activemq, the tests are failing. > I suggest remove the above directory before/after tests had run in this class. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FALCON-2325) Kerberos Service Token refresh does not happen
[ https://issues.apache.org/jira/browse/FALCON-2325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-2325: Summary: Kerberos Service Token refresh does not happen (was: Kerberos Service Key refresh does not happen) > Kerberos Service Token refresh does not happen > -- > > Key: FALCON-2325 > URL: https://issues.apache.org/jira/browse/FALCON-2325 > Project: Falcon > Issue Type: Bug >Reporter: Pallavi Rao >Assignee: Pallavi Rao >Priority: Major > > For both Prism and Falcon Servers, Kerberos ticket does not get refreshed > although, > AuthenticationInitializationService, does a > checkTGTAndReloginFromKeytab() periodically. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FALCON-2325) Kerberos Service Key refresh does not happen
[
https://issues.apache.org/jira/browse/FALCON-2325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16371045#comment-16371045
]
Pallavi Rao commented on FALCON-2325:
-
The only advantage of the method, checkTGTAndReloginFromKeytab() as opposed to
loginUserFromKeytab()
is that the method doesn't attempt actual login till the token is close to
expiry (80% of ticket life has elapsed).
Upon, investigation found that
UserGroupInformation.checkTGTAndReloginFromKeytab() has the following check:
{quote}if (isSecurityEnabled() && this.user.getAuthenticationMethod() ==
UserGroupInformation.AuthenticationMethod.KERBEROS && this.isKeytab)
{quote}
this.isKeytab consistently returns false, although initial login uses keytab.
As a result, this method call becomes a no-op.
The workaround to overcome this is to do a regular login, loginUserFromKeytab()
instead of checkTGTAndReloginFromKeytab(), till the issue is addressed in
hadoop-auth.
> Kerberos Service Key refresh does not happen
>
>
> Key: FALCON-2325
> URL: https://issues.apache.org/jira/browse/FALCON-2325
> Project: Falcon
> Issue Type: Bug
>Reporter: Pallavi Rao
>Assignee: Pallavi Rao
>Priority: Major
>
> For both Prism and Falcon Servers, Kerberos ticket does not get refreshed
> although,
> AuthenticationInitializationService, does a
> checkTGTAndReloginFromKeytab() periodically.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (FALCON-2325) Kerberos Service Key refresh does not happen
Pallavi Rao created FALCON-2325: --- Summary: Kerberos Service Key refresh does not happen Key: FALCON-2325 URL: https://issues.apache.org/jira/browse/FALCON-2325 Project: Falcon Issue Type: Bug Reporter: Pallavi Rao Assignee: Pallavi Rao For both Prism and Falcon Servers, Kerberos ticket does not get refreshed although, AuthenticationInitializationService, does a checkTGTAndReloginFromKeytab() periodically. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FALCON-2321) When Prism is Kerberized, it doesn't pass its token while making calls to Falcon Server
Pallavi Rao created FALCON-2321: --- Summary: When Prism is Kerberized, it doesn't pass its token while making calls to Falcon Server Key: FALCON-2321 URL: https://issues.apache.org/jira/browse/FALCON-2321 Project: Falcon Issue Type: Bug Reporter: Pallavi Rao Assignee: Pallavi Rao -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (FALCON-2320) Workaround for "Falcon is not buildable/testable with maven 3.5.1+"
[ https://issues.apache.org/jira/browse/FALCON-2320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao resolved FALCON-2320. - Resolution: Duplicate Fix Version/s: 0.11 trunk > Workaround for "Falcon is not buildable/testable with maven 3.5.1+" > --- > > Key: FALCON-2320 > URL: https://issues.apache.org/jira/browse/FALCON-2320 > Project: Falcon > Issue Type: Bug > Components: build-tools, prism, tests >Reporter: Denes Bodo >Priority: Critical > Fix For: trunk, 0.11 > > > Falcon can not be built/tested due to maven deffect: MNG-6298 and we should > apply the > [workaround|https://github.com/stoicflame/enunciate/issues/763#issuecomment-341767840] > in prism's pom.xml. > Build is tested locally, workaround seems okay. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (FALCON-2319) Falcon Build is failing on a clean state machine
[ https://issues.apache.org/jira/browse/FALCON-2319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao resolved FALCON-2319. - Resolution: Fixed Fix Version/s: trunk Thanks [~sandeep.samudrala] for addressing this. > Falcon Build is failing on a clean state machine > - > > Key: FALCON-2319 > URL: https://issues.apache.org/jira/browse/FALCON-2319 > Project: Falcon > Issue Type: Bug > Components: common >Affects Versions: trunk, 0.11 >Reporter: sandeep samudrala >Assignee: sandeep samudrala > Fix For: trunk, 0.11 > > > Falcon build is failing on a clean state machine with issues around enunciate > plugin -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (FALCON-2317) Update NOTICE to include references to JMS spec license
[
https://issues.apache.org/jira/browse/FALCON-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16312625#comment-16312625
]
Pallavi Rao commented on FALCON-2317:
-
Thanks [~zsombor] for your contribution. Have merged your changes.
> Update NOTICE to include references to JMS spec license
> ---
>
> Key: FALCON-2317
> URL: https://issues.apache.org/jira/browse/FALCON-2317
> Project: Falcon
> Issue Type: Bug
> Components: general
>Affects Versions: 0.9
>Reporter: Venkat Ranganathan
> Attachments: FALCON-2317.patch
>
>
> We need to include the following in the NOTICE file
> {quote}
> This product includes JMS specifications (https://javaee.github.io/jms-spec/)
> which is distributed under the Common Development and Distribution License
> (https://javaee.github.io/jms-spec/LICENSE)
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (FALCON-2317) Update NOTICE to include references to JMS spec license
[
https://issues.apache.org/jira/browse/FALCON-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pallavi Rao resolved FALCON-2317.
-
Resolution: Fixed
> Update NOTICE to include references to JMS spec license
> ---
>
> Key: FALCON-2317
> URL: https://issues.apache.org/jira/browse/FALCON-2317
> Project: Falcon
> Issue Type: Bug
> Components: general
>Affects Versions: 0.9
>Reporter: Venkat Ranganathan
> Attachments: FALCON-2317.patch
>
>
> We need to include the following in the NOTICE file
> {quote}
> This product includes JMS specifications (https://javaee.github.io/jms-spec/)
> which is distributed under the Common Development and Distribution License
> (https://javaee.github.io/jms-spec/LICENSE)
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (FALCON-2309) Create Release Notes
[ https://issues.apache.org/jira/browse/FALCON-2309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-2309: Attachment: RelaseNotes-ApacheFalcon-0.11.docx Team, please review the release notes. [~Praveen], feel free to make any changes. This should unblock 0.11 release. > Create Release Notes > > > Key: FALCON-2309 > URL: https://issues.apache.org/jira/browse/FALCON-2309 > Project: Falcon > Issue Type: Sub-task >Reporter: Pallavi Rao >Assignee: Pallavi Rao > Fix For: 0.11 > > Attachments: RelaseNotes-ApacheFalcon-0.11.docx > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (FALCON-2309) Create Release Notes
[ https://issues.apache.org/jira/browse/FALCON-2309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao reassigned FALCON-2309: --- Assignee: Pallavi Rao > Create Release Notes > > > Key: FALCON-2309 > URL: https://issues.apache.org/jira/browse/FALCON-2309 > Project: Falcon > Issue Type: Sub-task >Reporter: Pallavi Rao >Assignee: Pallavi Rao > Fix For: 0.11 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-2206) Enhance Test Falcon Unit to validate a dag of entities.
[ https://issues.apache.org/jira/browse/FALCON-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-2206: Issue Type: Improvement (was: Sub-task) Parent: (was: FALCON-2182) > Enhance Test Falcon Unit to validate a dag of entities. > --- > > Key: FALCON-2206 > URL: https://issues.apache.org/jira/browse/FALCON-2206 > Project: Falcon > Issue Type: Improvement > Components: extensions >Reporter: sandeep samudrala > > Enhance Test Falcon Unit tests to validate a dag of entities. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-2198) Update instance operation API to handle user extensions
[ https://issues.apache.org/jira/browse/FALCON-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-2198: Issue Type: Improvement (was: Sub-task) Parent: (was: FALCON-2182) > Update instance operation API to handle user extensions > --- > > Key: FALCON-2198 > URL: https://issues.apache.org/jira/browse/FALCON-2198 > Project: Falcon > Issue Type: Improvement > Components: extensions >Reporter: Pallavi Rao >Assignee: sandeep samudrala > > Existing schedule, suspend, resume APIs of Extension Manager need to be > modified to support user extensions. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (FALCON-2182) Add support for Falcon user extensions
[ https://issues.apache.org/jira/browse/FALCON-2182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao resolved FALCON-2182. - Resolution: Fixed Release Note: Resolving this as most of the sub-tasks are resolved. The ones remaining are nice to haves, which I'll move out of this task. > Add support for Falcon user extensions > -- > > Key: FALCON-2182 > URL: https://issues.apache.org/jira/browse/FALCON-2182 > Project: Falcon > Issue Type: New Feature > Components: extensions >Reporter: Pallavi Rao > Fix For: trunk, 0.11 > > Attachments: FalconUserExtensions (1).pdf, FalconUserExtensions.pdf > > > Currently server-side trusted extensions are supported (see FALCON-634 for > more details). > Need to extend the Falcon Extensions to support extensions built by users. > For example, lets say a user wants to add an extension for "data-quality > check". This shouldn't require it to be compiled and tested with Falcon > build. User should be able to add it on-the-fly (while the Falcon Server is > running) and other users should be able to discover it, and "instantiate" > this new extension. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-2182) Add support for Falcon user extensions
[ https://issues.apache.org/jira/browse/FALCON-2182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-2182: Fix Version/s: 0.11 trunk > Add support for Falcon user extensions > -- > > Key: FALCON-2182 > URL: https://issues.apache.org/jira/browse/FALCON-2182 > Project: Falcon > Issue Type: New Feature > Components: extensions >Reporter: Pallavi Rao > Fix For: trunk, 0.11 > > Attachments: FalconUserExtensions (1).pdf, FalconUserExtensions.pdf > > > Currently server-side trusted extensions are supported (see FALCON-634 for > more details). > Need to extend the Falcon Extensions to support extensions built by users. > For example, lets say a user wants to add an extension for "data-quality > check". This shouldn't require it to be compiled and tested with Falcon > build. User should be able to add it on-the-fly (while the Falcon Server is > running) and other users should be able to discover it, and "instantiate" > this new extension. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-2059) BacklogMetricEmitter Service for Falcon
[ https://issues.apache.org/jira/browse/FALCON-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-2059: Component/s: metrics > BacklogMetricEmitter Service for Falcon > > > Key: FALCON-2059 > URL: https://issues.apache.org/jira/browse/FALCON-2059 > Project: Falcon > Issue Type: Task > Components: metrics >Reporter: pavan kumar kolamuri >Assignee: pavan kumar kolamuri > Fix For: trunk, 0.11 > > > Backlog Metric Emitter service evaluates backlog for processes and emits > backlog metrics to graphite -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-2059) BacklogMetricEmitter Service for Falcon
[ https://issues.apache.org/jira/browse/FALCON-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-2059: Fix Version/s: 0.11 > BacklogMetricEmitter Service for Falcon > > > Key: FALCON-2059 > URL: https://issues.apache.org/jira/browse/FALCON-2059 > Project: Falcon > Issue Type: Task >Reporter: pavan kumar kolamuri >Assignee: pavan kumar kolamuri > Fix For: trunk, 0.11 > > > Backlog Metric Emitter service evaluates backlog for processes and emits > backlog metrics to graphite -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (FALCON-2309) Create Release Notes
Pallavi Rao created FALCON-2309: --- Summary: Create Release Notes Key: FALCON-2309 URL: https://issues.apache.org/jira/browse/FALCON-2309 Project: Falcon Issue Type: Sub-task Reporter: Pallavi Rao Fix For: 0.11 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (FALCON-2308) Create Change log
[ https://issues.apache.org/jira/browse/FALCON-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao resolved FALCON-2308. - Resolution: Fixed > Create Change log > - > > Key: FALCON-2308 > URL: https://issues.apache.org/jira/browse/FALCON-2308 > Project: Falcon > Issue Type: Sub-task >Reporter: Pallavi Rao >Assignee: Pallavi Rao > Fix For: 0.11 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-2196) Extensions User documentation
[ https://issues.apache.org/jira/browse/FALCON-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-2196: Summary: Extensions User documentation (was: User documentation) > Extensions User documentation > - > > Key: FALCON-2196 > URL: https://issues.apache.org/jira/browse/FALCON-2196 > Project: Falcon > Issue Type: Sub-task > Components: extensions >Reporter: Pallavi Rao >Assignee: sandeep samudrala > Fix For: trunk, 0.11 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-2196) User documentation
[ https://issues.apache.org/jira/browse/FALCON-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-2196: Fix Version/s: 0.11 trunk > User documentation > -- > > Key: FALCON-2196 > URL: https://issues.apache.org/jira/browse/FALCON-2196 > Project: Falcon > Issue Type: Sub-task > Components: extensions >Reporter: Pallavi Rao >Assignee: sandeep samudrala > Fix For: trunk, 0.11 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (FALCON-2196) User documentation
[ https://issues.apache.org/jira/browse/FALCON-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao resolved FALCON-2196. - Resolution: Fixed > User documentation > -- > > Key: FALCON-2196 > URL: https://issues.apache.org/jira/browse/FALCON-2196 > Project: Falcon > Issue Type: Sub-task > Components: extensions >Reporter: Pallavi Rao >Assignee: sandeep samudrala > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-2281) HiveDRTest tests are getting permissions denied
[
https://issues.apache.org/jira/browse/FALCON-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pallavi Rao updated FALCON-2281:
Component/s: general
> HiveDRTest tests are getting permissions denied
> ---
>
> Key: FALCON-2281
> URL: https://issues.apache.org/jira/browse/FALCON-2281
> Project: Falcon
> Issue Type: Bug
> Components: general
>Affects Versions: trunk
> Environment: Centos 6
>Reporter: Cheng Xu
>Assignee: Sowmya Ramesh
> Fix For: trunk, 0.11
>
>
> HiveDRTest tests are getting permissions denied.
> {noformat}
> 2016-11-17 09:31:22,681 INFO - [pool-28-thread-1:] ~
> java.lang.AssertionError: Status should be SUCCEEDED. Message: default/Failed
> to copy extension artifacts to clusterAbe0e31d0-180c1ef2
> CausedBy: Permission denied: user=falcon, access=READ,
> inode="/apps/falcon/extensions/mirroring/Events/HiveDRTest7df2bcd6/HiveDRTest7df2bcd6.id":hrt_qa:users:-rwx--
> at
> org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.check(FSPermissionChecker.java:319)
> at
> org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.checkPermission(FSPermissionChecker.java:219)
> at
> org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.checkPermission(FSPermissionChecker.java:190)
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkPermission(FSDirectory.java:1827)
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkPermission(FSDirectory.java:1811)
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkPathAccess(FSDirectory.java:1785)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getBlockLocationsInt(FSNamesystem.java:1868)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getBlockLocations(FSNamesystem.java:1837)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getBlockLocations(FSNamesystem.java:1750)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.getBlockLocations(NameNodeRpcServer.java:693)
> at
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.getBlockLocations(ClientNamenodeProtocolServerSideTranslatorPB.java:373)
> at
> org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:640)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:982)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2313)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2309)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1724)
> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2307)
> expected [SUCCEEDED] but found [FAILED]
> at org.testng.Assert.fail(Assert.java:94)
> at org.testng.Assert.failNotEquals(Assert.java:494)
> at org.testng.Assert.assertEquals(Assert.java:123)
> at
> org.apache.falcon.regression.core.util.AssertUtil.assertSucceeded(AssertUtil.java:199)
> at
> org.apache.falcon.regression.core.bundle.Bundle.submitClusters(Bundle.java:597)
> at
> org.apache.falcon.regression.core.bundle.Bundle.submitClusters(Bundle.java:590)
> at
> org.apache.falcon.regression.extensions.HiveDRTest.setUp(HiveDRTest.java:92)
> at
> org.apache.falcon.regression.extensions.HiveDRTest.drChangeCommentAndPropertyTest(HiveDRTest.java:452)
> 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
> org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84)
> at org.testng.internal.Invoker.invokeMethod(Invoker.java:714)
> at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901)
> at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231)
> at
> org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
> at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> (TestngListener:122)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (FALCON-2115) UT test failure on FalconCSRFFilterTest
[ https://issues.apache.org/jira/browse/FALCON-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-2115: Component/s: general > UT test failure on FalconCSRFFilterTest > --- > > Key: FALCON-2115 > URL: https://issues.apache.org/jira/browse/FALCON-2115 > Project: Falcon > Issue Type: Bug > Components: general >Reporter: Ying Zheng >Assignee: Ying Zheng > Fix For: trunk, 0.11 > > > Need to add the property falcon.security.csrf.header to startup properties > when testing custom header for CSRF filter. > Tests run: 5, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 1.186 sec <<< > FAILURE! - in org.apache.falcon.security.FalconCSRFFilterTest > testCSRFEnabledIncludeCustomHeaderFromBrowser(org.apache.falcon.security.FalconCSRFFilterTest) > Time elapsed: 0.012 sec <<< FAILURE! > org.mockito.exceptions.verification.NeverWantedButInvoked: > mockResponse.sendError( > 403, > "Missing Required Header for CSRF Vulnerability Protection" > ); > Never wanted here: > -> at > org.apache.falcon.security.FalconCSRFFilterTest.testCSRFEnabledIncludeCustomHeaderFromBrowser(FalconCSRFFilterTest.java:83) > But invoked here: > -> at > org.apache.falcon.security.RestCsrfPreventionFilter$ServletFilterHttpInteraction.sendError(RestCsrfPreventionFilter.java:173) > at > org.apache.falcon.security.FalconCSRFFilterTest.testCSRFEnabledIncludeCustomHeaderFromBrowser(FalconCSRFFilterTest.java:83) > testCSRFEnabledNoCustomHeaderFromBrowser(org.apache.falcon.security.FalconCSRFFilterTest) > Time elapsed: 0.003 sec <<< FAILURE! > org.mockito.exceptions.verification.TooManyActualInvocations: > mockResponse.sendError( > 403, > "Missing Required Header for CSRF Vulnerability Protection" > ); > Wanted 1 time: > -> at > org.apache.falcon.security.FalconCSRFFilterTest.testCSRFEnabledNoCustomHeaderFromBrowser(FalconCSRFFilterTest.java:73) > But was 2 times. Undesired invocation: > -> at > org.apache.falcon.security.RestCsrfPreventionFilter$ServletFilterHttpInteraction.sendError(RestCsrfPreventionFilter.java:173) > at > org.apache.falcon.security.FalconCSRFFilterTest.testCSRFEnabledNoCustomHeaderFromBrowser(FalconCSRFFilterTest.java:73) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-2259) Unregister an extension only if no extension jobs are dependant on the extension
[ https://issues.apache.org/jira/browse/FALCON-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-2259: Component/s: extensions > Unregister an extension only if no extension jobs are dependant on the > extension > > > Key: FALCON-2259 > URL: https://issues.apache.org/jira/browse/FALCON-2259 > Project: Falcon > Issue Type: Bug > Components: extensions >Reporter: sandeep samudrala >Assignee: sandeep samudrala > Fix For: trunk, 0.11 > > > Right now an extension can be unregistered irrespective of the any dependent > extensions. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-2284) Error while listing extension jobs
[
https://issues.apache.org/jira/browse/FALCON-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pallavi Rao updated FALCON-2284:
Component/s: extensions
> Error while listing extension jobs
> --
>
> Key: FALCON-2284
> URL: https://issues.apache.org/jira/browse/FALCON-2284
> Project: Falcon
> Issue Type: Bug
> Components: extensions
>Reporter: Richie Varghese
>Assignee: Pracheer Agarwal
> Fix For: trunk, 0.11
>
>
> I registered an extension and tried to list the instances of the extension
> and I got an error.
> {noformat}
> richie.varghese@falcon1001:~$ falcon extension -list -extensionName webExt
> ERROR: Not Found;Extension not found:/webExt
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (FALCON-2293) falcon extension fails for deletion if 2 extensions have same entity name
[ https://issues.apache.org/jira/browse/FALCON-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-2293: Component/s: extensions > falcon extension fails for deletion if 2 extensions have same entity name > -- > > Key: FALCON-2293 > URL: https://issues.apache.org/jira/browse/FALCON-2293 > Project: Falcon > Issue Type: Bug > Components: extensions >Reporter: sandeep samudrala >Assignee: sandeep samudrala > Fix For: trunk, 0.11 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-2219) Untracked files after falcon build
[ https://issues.apache.org/jira/browse/FALCON-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-2219: Component/s: general > Untracked files after falcon build > --- > > Key: FALCON-2219 > URL: https://issues.apache.org/jira/browse/FALCON-2219 > Project: Falcon > Issue Type: Bug > Components: general >Reporter: Praveen Adlakha >Assignee: Praveen Adlakha > Fix For: trunk, 0.11 > > > Hi All, > Once the falcon build completes we have : > unit/src/test/resources/falcon-extensions-0.11-SNAPSHOT-tests.jar > The above jar as untracked file.We should add it to the .gitignore file. > Thanks > Praveen -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-2121) If a feed does not exist on a cluster, process submission fails with NPE
[
https://issues.apache.org/jira/browse/FALCON-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pallavi Rao updated FALCON-2121:
Component/s: prism
> If a feed does not exist on a cluster, process submission fails with NPE
>
>
> Key: FALCON-2121
> URL: https://issues.apache.org/jira/browse/FALCON-2121
> Project: Falcon
> Issue Type: Bug
> Components: prism
>Affects Versions: trunk
>Reporter: Pallavi Rao
>Assignee: Pallavi Rao
> Fix For: trunk, 0.11
>
>
> The process definition:
> {noformat}
>
>
>
>
>
>
>
>
>
> ...
>
>
>
> {noformat}
> Feed "in" is present in "local" cluster, but, not in "local2" cluster. The
> following error occurs during process submission.
> {noformat}
> $ bin/falcon entity -submit -type process -file
> examples/entity/filesystem/pig-process.xml
> ERROR: Bad Request;default/java.lang.NullPointerException
> CausedBy: null
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (FALCON-2224) Change return type of extension APIs to APIResult
[ https://issues.apache.org/jira/browse/FALCON-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-2224: Component/s: extensions > Change return type of extension APIs to APIResult > - > > Key: FALCON-2224 > URL: https://issues.apache.org/jira/browse/FALCON-2224 > Project: Falcon > Issue Type: Bug > Components: extensions >Reporter: Praveen Adlakha >Assignee: Pracheer Agarwal > Fix For: trunk, 0.11 > > > Currently the return type of the extension API is String we should change it > to APIResult. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-2177) Improve error message when entity suspend fails
[
https://issues.apache.org/jira/browse/FALCON-2177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pallavi Rao updated FALCON-2177:
Component/s: (was: general)
prism
> Improve error message when entity suspend fails
> ---
>
> Key: FALCON-2177
> URL: https://issues.apache.org/jira/browse/FALCON-2177
> Project: Falcon
> Issue Type: Bug
> Components: prism
>Reporter: Pallavi Rao
>Assignee: Pallavi Rao
>Priority: Minor
> Fix For: trunk, 0.11
>
>
> f a process is completed and user tries to suspend the process falcon throws
> the following error :
> {noformat}
> dataqa@falcon1001:~$ falcon entity -type process -suspend -name Process-0
> ERROR: Bad Request;ua1/Process-0(process) is not scheduled
> {noformat}
> Status :
> {noformat}
> dataqa@falcon1001:~$ falcon entity -type process -status -name Process-0
> ua1/COMPLETED
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (FALCON-2028) HDFS extension: Validate and append/remove the scheme://authority for the paths
[
https://issues.apache.org/jira/browse/FALCON-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pallavi Rao updated FALCON-2028:
Component/s: extensions
> HDFS extension: Validate and append/remove the scheme://authority for the
> paths
> ---
>
> Key: FALCON-2028
> URL: https://issues.apache.org/jira/browse/FALCON-2028
> Project: Falcon
> Issue Type: Bug
> Components: extensions
>Reporter: Sowmya Ramesh
>Assignee: Sowmya Ramesh
> Fix For: trunk, 0.11
>
>
> In hdfs-mirroring-workflow.xml target EP is added only for target dir.
> {noformat}
> -sourcePaths
> ${sourceDir}
> -targetPath
> ${targetClusterFS}${targetDir}
> {noformat}
> in the req, if sourceDir is not sent as fully qualified paths then extension
> should generate fully qualified paths before submitting the process. For
> targetDir if passed it should be removed.
> e.g.
> {noformat}
> sourceDir=/user/ambari-qaqa/dr/test/primaryCluster/input1,
> /user/ambari-qaqa/dr/test/primaryCluster/input2
> After processing:
> sourceDir=hdfs://240.0.0.10:8020/user/ambari-qaqa/dr/test/primaryCluster/input1,
> hdfs://240.0.0.10:8020/user/ambari-qaqa/dr/test/primaryCluster/input2
> {noformat}
> Also, if user has already specified the fully qualified path then it should
> not be added for sourceDir but it should be removed for targetDir
> {noformat}
> sourceDir=hdfs://240.0.0.10:8020/user/ambari-qa/dr/test/primaryCluster/input1,
> hdfs://240.0.0.10:8020/user/ambari-qa/dr/test/primaryCluster/input2
> After processing:
> sourceDir=hdfs://240.0.0.10:8020/user/ambari-qa/dr/test/primaryCluster/input1,
> hdfs://240.0.0.10:8020/user/ambari-qa/dr/test/primaryCluster/input2
>
> targetDir=hdfs://240.0.0.11:8020/user/ambari-qa/dr/test/backupCluster/outputs
> After processing:
> targetDir=/user/ambari-qa/dr/test/backupCluster/outputs
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (FALCON-2177) Improve error message when entity suspend fails
[
https://issues.apache.org/jira/browse/FALCON-2177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pallavi Rao updated FALCON-2177:
Component/s: general
> Improve error message when entity suspend fails
> ---
>
> Key: FALCON-2177
> URL: https://issues.apache.org/jira/browse/FALCON-2177
> Project: Falcon
> Issue Type: Bug
> Components: prism
>Reporter: Pallavi Rao
>Assignee: Pallavi Rao
>Priority: Minor
> Fix For: trunk, 0.11
>
>
> f a process is completed and user tries to suspend the process falcon throws
> the following error :
> {noformat}
> dataqa@falcon1001:~$ falcon entity -type process -suspend -name Process-0
> ERROR: Bad Request;ua1/Process-0(process) is not scheduled
> {noformat}
> Status :
> {noformat}
> dataqa@falcon1001:~$ falcon entity -type process -status -name Process-0
> ua1/COMPLETED
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (FALCON-2230) Extension API failure after APIResult changes
[ https://issues.apache.org/jira/browse/FALCON-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-2230: Component/s: extensions > Extension API failure after APIResult changes > - > > Key: FALCON-2230 > URL: https://issues.apache.org/jira/browse/FALCON-2230 > Project: Falcon > Issue Type: Bug > Components: extensions >Reporter: Pracheer Agarwal >Assignee: Pracheer Agarwal > Fix For: trunk, 0.11 > > > Extension API failure after APIResult changes -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-2080) Exceptions in the log
[
https://issues.apache.org/jira/browse/FALCON-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pallavi Rao updated FALCON-2080:
Component/s: general
> Exceptions in the log
> -
>
> Key: FALCON-2080
> URL: https://issues.apache.org/jira/browse/FALCON-2080
> Project: Falcon
> Issue Type: Bug
> Components: general
>Reporter: Praveen Adlakha
>Assignee: Praveen Adlakha
> Fix For: trunk, 0.11
>
>
> Hi All,
> We are getting the following exceptions in the logs :
> {code}
> ouldn't find status for Entity:ProcessInstanceRerunTest-agregator-10,
> cluster:local, entityTypePROCESS, nominalTimeWed Jul 13 15:35:00 IST 2016
> (FeedSLA:473)
> org.apache.falcon.FalconException: java.lang.IllegalStateException: No user
> logged into the system : java.lang.IllegalStateException: No user logged into
> the system
> at
> org.apache.falcon.workflow.engine.OozieWorkflowEngine.findBundles(OozieWorkflowEngine.java:362)
> at
> org.apache.falcon.workflow.engine.OozieWorkflowEngine.findBundles(OozieWorkflowEngine.java:372)
> at
> org.apache.falcon.workflow.engine.OozieWorkflowEngine.getCoordActions(OozieWorkflowEngine.java:1104)
> at
> org.apache.falcon.workflow.engine.OozieWorkflowEngine.doJobAction(OozieWorkflowEngine.java:666)
> at
> org.apache.falcon.workflow.engine.OozieWorkflowEngine.doJobAction(OozieWorkflowEngine.java:737)
> at
> org.apache.falcon.workflow.engine.OozieWorkflowEngine.getStatus(OozieWorkflowEngine.java:598)
> at
> org.apache.falcon.service.EntitySLAMonitoringService.checkEntityInstanceAvailability(EntitySLAMonitoringService.java:451)
> at
> org.apache.falcon.service.EntitySLAMonitoringService.checkPendingInstanceAvailability(EntitySLAMonitoringService.java:430)
> at
> org.apache.falcon.service.EntitySLAMonitoringService.access$200(EntitySLAMonitoringService.java:72)
> at
> org.apache.falcon.service.EntitySLAMonitoringService$Monitor.run(EntitySLAMonitoringService.java:349)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (FALCON-2072) Hive2 URLs in Falcon should allow additional configuration elements in the URL
[ https://issues.apache.org/jira/browse/FALCON-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-2072: Component/s: general > Hive2 URLs in Falcon should allow additional configuration elements in the URL > -- > > Key: FALCON-2072 > URL: https://issues.apache.org/jira/browse/FALCON-2072 > Project: Falcon > Issue Type: Bug > Components: general >Affects Versions: 0.6.1, 0.8, 0.9, 0.10 >Reporter: Venkat Ranganathan >Assignee: Sowmya Ramesh > Fix For: trunk, 0.11 > > > When configuring the Hive2 URLs, SSL, trust store password may need to be > specified. > Furthermore, the URL can be configured to use zookeeper discovery mode where > zookeeper can be used as a single point of configuration changes that are > automatically available to the Hive2 clients. This mode also supports HA > for the HiveServer -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-2116) Queue defined in is not getting used in actual retention job
[
https://issues.apache.org/jira/browse/FALCON-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pallavi Rao updated FALCON-2116:
Component/s: retention
> Queue defined in is not getting used in actual retention job
> --
>
> Key: FALCON-2116
> URL: https://issues.apache.org/jira/browse/FALCON-2116
> Project: Falcon
> Issue Type: Bug
> Components: retention
>Reporter: sandeep samudrala
>Assignee: sandeep samudrala
> Fix For: trunk, 0.11
>
>
> Following feed definition segment is not working properly, Both replication
> and retention jobs are running in "m10n" queue and queue from retention-stage
> is not getting picked up:
> {noformat}
>
>
>
>
>
>
> hours(1)
> default
> NORMAL
>
> value="days(10)"/>
>
>
>
> {noformat}
> Here we have a feed which replicates data from local to global cluster. We
> have queue "m10n" in global, but not in local colos. So we have specified
> "default" queue for retention jobs and "m10n" for replication jobs.
> But both are getting "m10n" queue. Due to which retention jobs in local colos
> are getting suspended.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (FALCON-2118) Proposal for new UI changes for FALCON
[ https://issues.apache.org/jira/browse/FALCON-2118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-2118: Component/s: falcon-ui > Proposal for new UI changes for FALCON > -- > > Key: FALCON-2118 > URL: https://issues.apache.org/jira/browse/FALCON-2118 > Project: Falcon > Issue Type: Bug > Components: falcon-ui >Affects Versions: 0.10 >Reporter: Venkat Ranganathan >Assignee: Venkat Ranganathan > Fix For: trunk, 0.11 > > > This tries to improve on the current UI. >1. Fix the layout so that we have single tabs for various entity screens >2. Reduce the number of fields by default and move rarely changed fields > to advanced option >3. More tool tips (still a WIP) >4. Better UI for some fields (permissions be more visual instead of > expecting an octal string for example) > > This is to get some feedback on these changes and continue on this. > There are also discussions on creating a full UI framework say using Django > or Flask or similar stacks. This can be used to drive those discussions, > improvements also -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-2120) falcon-regression build is failing because of CLI and hive changes
[
https://issues.apache.org/jira/browse/FALCON-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pallavi Rao updated FALCON-2120:
Component/s: regression
> falcon-regression build is failing because of CLI and hive changes
> --
>
> Key: FALCON-2120
> URL: https://issues.apache.org/jira/browse/FALCON-2120
> Project: Falcon
> Issue Type: Bug
> Components: regression
>Reporter: Praveen Adlakha
>Assignee: Praveen Adlakha
> Fix For: trunk, 0.11
>
>
> Hi All,
> Regression build is failing with two errors :
> {code}
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Falcon Regression ... SUCCESS [ 0.369
> s]
> [INFO] Apache Falcon Regression Suite Core FAILURE [ 0.343
> s]
> [INFO] Apache Falcon Regression Suite . SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 1.082 s
> [INFO] Finished at: 2016-08-23T12:51:39+05:30
> [INFO] Final Memory: 21M/303M
> [INFO]
>
> [ERROR] Failed to execute goal on project falcon-merlin-core: Could not
> resolve dependencies for project
> org.apache.falcon.regression:falcon-merlin-core:jar:0.11-SNAPSHOT: Failure to
> find org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde in
> http://repo1.maven.org/maven2 was cached in the local repository, resolution
> will not be reattempted until the update interval of central has elapsed or
> updates are forced -> [Help 1]
> [ERROR]
> {code}
> Second:
> {code}
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Falcon Regression ... SUCCESS [ 1.964
> s]
> [INFO] Apache Falcon Regression Suite Core FAILURE [ 3.604
> s]
> [INFO] Apache Falcon Regression Suite . SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 5.732 s
> [INFO] Finished at: 2016-08-23T12:56:16+05:30
> [INFO] Final Memory: 63M/799M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
> (default-compile) on project falcon-merlin-core: Compilation failure:
> Compilation failure:
> [ERROR]
> /home/praveen/git/myfalcon/falcon/falcon-regression/merlin-core/src/main/java/org/apache/falcon/regression/core/bundle/Bundle.java:[22,28]
> error: package org.apache.falcon.cli does not exist
> [ERROR]
> /home/praveen/git/myfalcon/falcon/falcon-regression/merlin-core/src/main/java/org/apache/falcon/regression/Entities/RecipeMerlin.java:[29,28]
> error: package org.apache.falcon.cli does not exist
> [ERROR]
> /home/praveen/git/myfalcon/falcon/falcon-regression/merlin-core/src/main/java/org/apache/falcon/regression/Entities/RecipeMerlin.java:[79,20]
> error: package FalconCLI does not exist
> [ERROR]
> /home/praveen/git/myfalcon/falcon/falcon-regression/merlin-core/src/main/java/org/apache/falcon/regression/Entities/RecipeMerlin.java:[83,21]
> error: package FalconCLI does not exist
> [ERROR]
> /home/praveen/git/myfalcon/falcon/falcon-regression/merlin-core/src/main/java/org/apache/falcon/regression/Entities/RecipeMerlin.java:[243,52]
> error: package FalconCLI does not exist
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (FALCON-2263) Deletion of entities for an extension has to have a specific order of deleting processes first and then feeds
[ https://issues.apache.org/jira/browse/FALCON-2263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-2263: Component/s: extensions > Deletion of entities for an extension has to have a specific order of > deleting processes first and then feeds > - > > Key: FALCON-2263 > URL: https://issues.apache.org/jira/browse/FALCON-2263 > Project: Falcon > Issue Type: Bug > Components: extensions >Reporter: sandeep samudrala >Assignee: sandeep samudrala > Fix For: trunk, 0.11 > > > Deletion of entities for an extension has to have a specific order of > deleting processes first and then feeds. > As of now it tries to delete feeds first and fails for dependency on the > dependent process -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-2175) java.lang.IllegalArgumentException in LogMover service
[
https://issues.apache.org/jira/browse/FALCON-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pallavi Rao updated FALCON-2175:
Component/s: general
> java.lang.IllegalArgumentException in LogMover service
> ---
>
> Key: FALCON-2175
> URL: https://issues.apache.org/jira/browse/FALCON-2175
> Project: Falcon
> Issue Type: Bug
> Components: general
>Reporter: Pallavi Rao
>Assignee: Pallavi Rao
> Fix For: trunk, 0.11
>
>
> 2016-10-25 19:19:02,581 DEBUG - [ActiveMQ Session Task-12:] ~ Sending
> workflow end notification to listeners with context :
> WorkflowExecutionContext{{nominalTime=2016-10-25-19-00,
> workflowEndTime=1477423129270, parentId=008-161025181049892-oozie-oozi-C,
> entityType=PROCESS, cluster=ProcessSLATest-corp-b16d2875,
> workflowId=008-161025181049892-oozie-oozi-C@11, operation=GENERATE,
> status=TIMEDOUT, entityName=ProcessSLATest-1, workflowUser=dataqa,
> contextType=COORDINATOR_ACTION,
> subflowId=008-161025181049892-oozie-oozi-C@11@user-action,
> workflowStartTime=1477423142578}} (WorkflowJobEndNotificationService:234)
> 2016-10-25 19:19:02,581 ERROR - [pool-4-thread-5:] ~ Exception in log mover:
> (JobLogMover:140)
> java.lang.IllegalArgumentException: oozieUrl cannot be null
> at
> org.apache.oozie.client.OozieClient.notEmpty(OozieClient.java:2789)
> at
> org.apache.oozie.client.OozieClient.(OozieClient.java:260)
> at
> org.apache.falcon.logging.JobLogMover.run(JobLogMover.java:87)
> at
> org.apache.falcon.logging.JobLogMover.moveLog(JobLogMover.java:78)
> at
> org.apache.falcon.service.LogMoverService$LogMover.run(LogMoverService.java:118)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (FALCON-2171) When feed from multiple colos are replicated, the colo folders get overwritten
[ https://issues.apache.org/jira/browse/FALCON-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-2171: Component/s: replication > When feed from multiple colos are replicated, the colo folders get overwritten > -- > > Key: FALCON-2171 > URL: https://issues.apache.org/jira/browse/FALCON-2171 > Project: Falcon > Issue Type: Bug > Components: replication >Reporter: Pallavi Rao >Assignee: Pallavi Rao > Fix For: trunk, 0.11 > > > Regression caused by FALCON-1844. > Work around as discussed is to add the following property to the feed > definition: > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-2203) Minor issues in EntitySLAmonitoring
[ https://issues.apache.org/jira/browse/FALCON-2203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-2203: Component/s: process > Minor issues in EntitySLAmonitoring > > > Key: FALCON-2203 > URL: https://issues.apache.org/jira/browse/FALCON-2203 > Project: Falcon > Issue Type: Bug > Components: process >Reporter: Praveen Adlakha >Assignee: Praveen Adlakha > Fix For: trunk, 0.11 > > > Hi All, > This issue is for tracking is minor issues in EntitySLAMonitoring. > The code in this pull request was written by [~sandeep.samudrala] > Thanks > Praveen -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-2305) workflow metrics thread failures
[ https://issues.apache.org/jira/browse/FALCON-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-2305: Component/s: metrics > workflow metrics thread failures > > > Key: FALCON-2305 > URL: https://issues.apache.org/jira/browse/FALCON-2305 > Project: Falcon > Issue Type: Bug > Components: metrics >Reporter: Praveen Adlakha >Assignee: Praveen Adlakha > Fix For: trunk, 0.11 > > > BacklogMetricEmitterService.BacklogCheckService.run method. > Line 420 : wfEngine.getStatus - If this call fails for whatever reason for > one entity, it exits the loop and doesn't complete the loop for rest of the > entities. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-2303) Backloginmins is not getting updated
[ https://issues.apache.org/jira/browse/FALCON-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-2303: Component/s: metrics > Backloginmins is not getting updated > - > > Key: FALCON-2303 > URL: https://issues.apache.org/jira/browse/FALCON-2303 > Project: Falcon > Issue Type: Bug > Components: metrics >Reporter: Praveen Adlakha >Assignee: Praveen Adlakha > Fix For: trunk, 0.11 > > > There are cases where backlog is not getting accumulated even when there are > multiple killed instances. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-2111) Build failed due to checkstyle violation
[
https://issues.apache.org/jira/browse/FALCON-2111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pallavi Rao updated FALCON-2111:
Component/s: general
> Build failed due to checkstyle violation
> -
>
> Key: FALCON-2111
> URL: https://issues.apache.org/jira/browse/FALCON-2111
> Project: Falcon
> Issue Type: Bug
> Components: general
>Affects Versions: trunk
>Reporter: Balu Vellanki
>Assignee: Balu Vellanki
> Fix For: trunk, 0.11
>
>
> {code}
> [INFO] Exclude: **/falcon-cli-hist.log
> [INFO]
> [INFO] --- maven-checkstyle-plugin:2.9.1:check (checkstyle-check) @
> falcon-common ---
> [INFO] Starting audit...
> :53:
> Line is longer than 120 characters.
> Audit done.
> [INFO] There are 1 checkstyle errors.
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Falcon .. SUCCESS [ 14.095
> s]
> [INFO] Apache Falcon UI ... SUCCESS [ 15.386
> s]
> [INFO] Build Tools SUCCESS [ 6.158
> s]
> [INFO] Apache Falcon Java client .. SUCCESS [ 41.506
> s]
> [INFO] Apache Falcon Shell SUCCESS [ 15.622
> s]
> [INFO] Apache Falcon Metrics .. SUCCESS [ 17.478
> s]
> [INFO] Apache Falcon Hadoop Dependencies .. SUCCESS [ 14.766
> s]
> [INFO] Apache Falcon Test Utility . SUCCESS [ 13.427
> s]
> [INFO] Apache Falcon Commons .. FAILURE [02:34
> min]
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (FALCON-1776) Process instance update in titan DB based on JMS notifications on coordinator actions
[ https://issues.apache.org/jira/browse/FALCON-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-1776: Component/s: process > Process instance update in titan DB based on JMS notifications on coordinator > actions > - > > Key: FALCON-1776 > URL: https://issues.apache.org/jira/browse/FALCON-1776 > Project: Falcon > Issue Type: Improvement > Components: process >Reporter: Ying Zheng >Assignee: Ying Zheng > Fix For: trunk, 0.11 > > > In JMS notifications from the coordinator action, it is not guaranteed to > provide information on timestamp and user workflow version. Need to allow > these properties to be optional when adding process instance to titan DB. > Also need to address the different format when there is no input/output feed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-2288) Remove job_name validations for trusted extensions
[ https://issues.apache.org/jira/browse/FALCON-2288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-2288: Component/s: extensions > Remove job_name validations for trusted extensions > -- > > Key: FALCON-2288 > URL: https://issues.apache.org/jira/browse/FALCON-2288 > Project: Falcon > Issue Type: Improvement > Components: extensions >Reporter: Pracheer Agarwal >Assignee: Pracheer Agarwal > Fix For: trunk, 0.11 > > > While submitting a job for trusted extensions, job name is provided in conf > as well as from the user also. Remove the job_name property form conf and > take the job name passed by user. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-2044) Persist Process stats in db
[ https://issues.apache.org/jira/browse/FALCON-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-2044: Component/s: metrics > Persist Process stats in db > --- > > Key: FALCON-2044 > URL: https://issues.apache.org/jira/browse/FALCON-2044 > Project: Falcon > Issue Type: Improvement > Components: metrics >Reporter: Praveen Adlakha >Assignee: Praveen Adlakha > Fix For: trunk, 0.11 > > > Hi All, > We should persist stats like process name,colo,nominal time ,delay time and > processing time in db so that we can do trend analysis over the performance > of the process. > I am thinking to persist it in the falcon DB if anyone has better approach > regarding this please provide there input. > Thanks > Praveen -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-1944) Ability to provide additional DistCP options for mirroring extensions and feed replication
[ https://issues.apache.org/jira/browse/FALCON-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-1944: Component/s: replication extensions > Ability to provide additional DistCP options for mirroring extensions and > feed replication > -- > > Key: FALCON-1944 > URL: https://issues.apache.org/jira/browse/FALCON-1944 > Project: Falcon > Issue Type: Improvement > Components: extensions, replication >Reporter: Sowmya Ramesh >Assignee: Sowmya Ramesh > Fix For: trunk, 0.11 > > > Mirroring extensions and feed replication should have the ability to provide > additional DistCp options. Also handle TDE enabled option -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-2119) Minor Licensing Issue
[ https://issues.apache.org/jira/browse/FALCON-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-2119: Component/s: license > Minor Licensing Issue > - > > Key: FALCON-2119 > URL: https://issues.apache.org/jira/browse/FALCON-2119 > Project: Falcon > Issue Type: Improvement > Components: license >Reporter: Ajay Yadava >Assignee: Ajay Yadava > Fix For: trunk, 0.11 > > > falcon-sources-0.10/falcon-ui/app/css/styles/angular-notify.less > is actually not an original work and is exactly same as MIT Licensed (but not > mentioned in LICENSE.txt) except for few commented lines. > https://github.com/cgross/angular-notify/blob/master/angular-notify.css -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-2173) BacklogEmitterService should emit 0 for process which donot have backlog
[ https://issues.apache.org/jira/browse/FALCON-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-2173: Component/s: metrics > BacklogEmitterService should emit 0 for process which donot have backlog > > > Key: FALCON-2173 > URL: https://issues.apache.org/jira/browse/FALCON-2173 > Project: Falcon > Issue Type: Improvement > Components: metrics >Reporter: Praveen Adlakha >Assignee: Praveen Adlakha > Fix For: trunk, 0.11 > > > Hi All, > Currently the backlog emitter service doesn't emit anything if the process > does not have a backlog ,ideally it should emit zero in such cases. > Thanks > Praveen -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-2039) Move falcon post processing to falcon server and remove post processing action from falcon workflow
[ https://issues.apache.org/jira/browse/FALCON-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-2039: Component/s: general > Move falcon post processing to falcon server and remove post processing > action from falcon workflow > --- > > Key: FALCON-2039 > URL: https://issues.apache.org/jira/browse/FALCON-2039 > Project: Falcon > Issue Type: Improvement > Components: general >Reporter: sandeep samudrala >Assignee: Praveen Adlakha > Fix For: trunk, 0.11 > > > Move falcon post processing to falcon server and remove post processing > action from falcon workflow. > Currently challenges with post-processing. > 1) In case of post processing failures, the workflow status goes into > killed/failed. > 2) Extra container being wasted for post processing action in the workflow, > which can be avoided if it can be moved to falcon server itself. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-2170) Umbrella jira for bugs in EntitySLAMonitoring and BacklogEmitter service
[ https://issues.apache.org/jira/browse/FALCON-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-2170: Component/s: metrics > Umbrella jira for bugs in EntitySLAMonitoring and BacklogEmitter service > - > > Key: FALCON-2170 > URL: https://issues.apache.org/jira/browse/FALCON-2170 > Project: Falcon > Issue Type: Improvement > Components: metrics >Reporter: Praveen Adlakha >Assignee: Praveen Adlakha > Fix For: trunk, 0.11 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-2077) Api support for Process SLA
[ https://issues.apache.org/jira/browse/FALCON-2077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-2077: Component/s: process > Api support for Process SLA > > > Key: FALCON-2077 > URL: https://issues.apache.org/jira/browse/FALCON-2077 > Project: Falcon > Issue Type: Improvement > Components: process >Reporter: Praveen Adlakha >Assignee: Praveen Adlakha > Fix For: trunk, 0.11 > > > Hi All, > Right now API only supports feed sla monitoring code for process SLA is > already checked in need to extend the api to support process also. > Thanks > Praveen -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-2123) Make Blocking Queue configurable in LogMoverService
[ https://issues.apache.org/jira/browse/FALCON-2123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-2123: Component/s: general > Make Blocking Queue configurable in LogMoverService > --- > > Key: FALCON-2123 > URL: https://issues.apache.org/jira/browse/FALCON-2123 > Project: Falcon > Issue Type: Improvement > Components: general >Reporter: Praveen Adlakha >Assignee: Praveen Adlakha > Fix For: trunk, 0.11 > > > Hi All, > Right now the queue size is hard coded to 50 which might be fine in > production but its better to have it configurable. > Thanks > Praveen -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-1780) Add falcon-cli executable and link that to falcon executable when no arguments are provided
[ https://issues.apache.org/jira/browse/FALCON-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-1780: Component/s: client > Add falcon-cli executable and link that to falcon executable when no > arguments are provided > --- > > Key: FALCON-1780 > URL: https://issues.apache.org/jira/browse/FALCON-1780 > Project: Falcon > Issue Type: Sub-task > Components: client >Reporter: Rajat Khandelwal >Assignee: Praveen Adlakha > Fix For: trunk, 0.11 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-2258) Improve error message for definition/describe api in case extension does not exist
[ https://issues.apache.org/jira/browse/FALCON-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-2258: Component/s: extensions > Improve error message for definition/describe api in case extension does not > exist > -- > > Key: FALCON-2258 > URL: https://issues.apache.org/jira/browse/FALCON-2258 > Project: Falcon > Issue Type: Sub-task > Components: extensions >Reporter: sandeep samudrala >Assignee: sandeep samudrala > Fix For: trunk, 0.11 > > > Extension check is expecting a single result set, causing failure of not > being found. This has to be checked for result set and send the response > message accordingly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-2082) Add CSRF filter for REST APIs
[ https://issues.apache.org/jira/browse/FALCON-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-2082: Component/s: prism > Add CSRF filter for REST APIs > - > > Key: FALCON-2082 > URL: https://issues.apache.org/jira/browse/FALCON-2082 > Project: Falcon > Issue Type: New Feature > Components: prism >Reporter: Ying Zheng >Assignee: Ying Zheng > Fix For: trunk, 0.11 > > Attachments: Screen Shot 2016-07-19 at 4.54.29 PM.png > > > A CSRF filter was added to Hadoop common > (https://issues.apache.org/jira/browse/HADOOP-12691). This JIRA is to > integrate this filter into Falcon REST APIs and provide the user an option to > enable CSRF filter. Also allow users to configure custom header and browser > agents. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-1612) Add Metadata commands to Falcon spring-shell CLI
[ https://issues.apache.org/jira/browse/FALCON-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-1612: Component/s: client > Add Metadata commands to Falcon spring-shell CLI > > > Key: FALCON-1612 > URL: https://issues.apache.org/jira/browse/FALCON-1612 > Project: Falcon > Issue Type: Sub-task > Components: client >Reporter: Rajat Khandelwal >Assignee: Praveen Adlakha > Fix For: trunk, 0.11 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-2205) describe for non trusted extension
[ https://issues.apache.org/jira/browse/FALCON-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-2205: Component/s: extensions > describe for non trusted extension > -- > > Key: FALCON-2205 > URL: https://issues.apache.org/jira/browse/FALCON-2205 > Project: Falcon > Issue Type: Sub-task > Components: extensions >Reporter: Praveen Adlakha >Assignee: Praveen Adlakha > Fix For: trunk, 0.11 > > > Hi All, > Currently describe api works only for trusted extension need to extend that > to handle the other extension too. > Thanks > Praveen -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-2153) Resetting Gauge value in BacklogEmitterService
[ https://issues.apache.org/jira/browse/FALCON-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-2153: Component/s: common > Resetting Gauge value in BacklogEmitterService > -- > > Key: FALCON-2153 > URL: https://issues.apache.org/jira/browse/FALCON-2153 > Project: Falcon > Issue Type: Sub-task > Components: common >Reporter: Praveen Adlakha >Assignee: Praveen Adlakha > Fix For: trunk, 0.11 > > > Hi All, > Currently, BacklogEmitter Service does not reset the gauge value to zero in > case the process last instance which has missed slaHigh has finished and > there is no more backlog. > The same is true when the process gets deleted. > In both the above cases the graph on the graphite will be straight line. > Thanks > Praveen -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-2181) Support for storing metadata of non trusted recipe
[ https://issues.apache.org/jira/browse/FALCON-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-2181: Component/s: extensions > Support for storing metadata of non trusted recipe > --- > > Key: FALCON-2181 > URL: https://issues.apache.org/jira/browse/FALCON-2181 > Project: Falcon > Issue Type: Sub-task > Components: extensions >Reporter: Praveen Adlakha >Assignee: Praveen Adlakha > Fix For: trunk, 0.11 > > > Hi All, > We are planning to add support of non trusted recipe in falcon.Will be adding > the metadata in the database. > Will add more details with schema etc in comments. > Thanks > Praveen -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-2186) Rest api to get details of an extension
[ https://issues.apache.org/jira/browse/FALCON-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-2186: Component/s: extensions > Rest api to get details of an extension > --- > > Key: FALCON-2186 > URL: https://issues.apache.org/jira/browse/FALCON-2186 > Project: Falcon > Issue Type: Sub-task > Components: extensions >Reporter: Praveen Adlakha >Assignee: Praveen Adlakha > Fix For: trunk, 0.11 > > > Hi All, > Need to add a rest api to get the location of extension. > Thanks > Praveen -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-2184) Support to delete a non trusted recipe metadata from server
[ https://issues.apache.org/jira/browse/FALCON-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-2184: Component/s: extensions > Support to delete a non trusted recipe metadata from server > --- > > Key: FALCON-2184 > URL: https://issues.apache.org/jira/browse/FALCON-2184 > Project: Falcon > Issue Type: Sub-task > Components: extensions >Reporter: Praveen Adlakha >Assignee: Praveen Adlakha > Fix For: trunk, 0.11 > > > Hi All, > As suggested in Falcon 2181 we will be cooking non trusted recipes on the > client. > We need to register and delete metadata from the server.In this jira will be > adding rest api and client support for deletion of the jira. > Thanks > Praveen -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-1611) Add admin commands to Falcon spring-shell CLI
[ https://issues.apache.org/jira/browse/FALCON-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-1611: Component/s: client > Add admin commands to Falcon spring-shell CLI > - > > Key: FALCON-1611 > URL: https://issues.apache.org/jira/browse/FALCON-1611 > Project: Falcon > Issue Type: Sub-task > Components: client >Reporter: Rajat Khandelwal >Assignee: Praveen Adlakha > Fix For: trunk, 0.11 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-1610) Add instance commands to Falcon spring-shell CLI
[ https://issues.apache.org/jira/browse/FALCON-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-1610: Component/s: client > Add instance commands to Falcon spring-shell CLI > > > Key: FALCON-1610 > URL: https://issues.apache.org/jira/browse/FALCON-1610 > Project: Falcon > Issue Type: Sub-task > Components: client >Reporter: Rajat Khandelwal >Assignee: Praveen Adlakha > Fix For: trunk, 0.11 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (FALCON-2308) Create Change log
[ https://issues.apache.org/jira/browse/FALCON-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16210835#comment-16210835 ] Pallavi Rao commented on FALCON-2308: - PR -> https://github.com/apache/falcon/pull/389 > Create Change log > - > > Key: FALCON-2308 > URL: https://issues.apache.org/jira/browse/FALCON-2308 > Project: Falcon > Issue Type: Sub-task >Reporter: Pallavi Rao >Assignee: Pallavi Rao > Fix For: 0.11 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (FALCON-2308) Create Change log
[ https://issues.apache.org/jira/browse/FALCON-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16210812#comment-16210812 ] Pallavi Rao commented on FALCON-2308: - Have documented the steps here -> https://cwiki.apache.org/confluence/display/FALCON/How+to+create+Change+Log+for+a+release It is just one way of creating the change log. There can be better/easier ways. > Create Change log > - > > Key: FALCON-2308 > URL: https://issues.apache.org/jira/browse/FALCON-2308 > Project: Falcon > Issue Type: Sub-task >Reporter: Pallavi Rao >Assignee: Pallavi Rao > Fix For: 0.11 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (FALCON-2308) Create Change log
Pallavi Rao created FALCON-2308: --- Summary: Create Change log Key: FALCON-2308 URL: https://issues.apache.org/jira/browse/FALCON-2308 Project: Falcon Issue Type: Sub-task Reporter: Pallavi Rao Assignee: Pallavi Rao Fix For: 0.11 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-2303) Backloginmins is not getting updated
[ https://issues.apache.org/jira/browse/FALCON-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao updated FALCON-2303: Fix Version/s: 0.11 > Backloginmins is not getting updated > - > > Key: FALCON-2303 > URL: https://issues.apache.org/jira/browse/FALCON-2303 > Project: Falcon > Issue Type: Bug >Reporter: Praveen Adlakha >Assignee: Praveen Adlakha > Fix For: trunk, 0.11 > > > There are cases where backlog is not getting accumulated even when there are > multiple killed instances. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (FALCON-2297) Falcon 0.11 release
[ https://issues.apache.org/jira/browse/FALCON-2297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao resolved FALCON-2297. - Resolution: Duplicate > Falcon 0.11 release > --- > > Key: FALCON-2297 > URL: https://issues.apache.org/jira/browse/FALCON-2297 > Project: Falcon > Issue Type: Task >Reporter: Praveen Adlakha >Assignee: Praveen Adlakha > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (FALCON-2303) Backloginmins is not getting updated
[ https://issues.apache.org/jira/browse/FALCON-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao resolved FALCON-2303. - Resolution: Fixed Fix Version/s: trunk > Backloginmins is not getting updated > - > > Key: FALCON-2303 > URL: https://issues.apache.org/jira/browse/FALCON-2303 > Project: Falcon > Issue Type: Bug >Reporter: Praveen Adlakha >Assignee: Praveen Adlakha > Fix For: trunk > > > There are cases where backlog is not getting accumulated even when there are > multiple killed instances. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (FALCON-2299) Adding custom engine in Apache Falcon
[ https://issues.apache.org/jira/browse/FALCON-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16110514#comment-16110514 ] Pallavi Rao commented on FALCON-2299: - [~Aniketmo], Falcon's design is quite well-structured in terms ease of adding a new execution engine. However, it does not follow a plugin/extension model, where users can just plug a new engine in. You will have to make changes to the core components of Falcon. If you have a good use case for supporting a generic engine, you can branch off the code and work on the same. You will get the community's input/help along the way. Also, just wanted to point out that pig, hive and spark are also internally translated to corresponding Oozie actions. So, when you say an execution engine, I'm not sure if you are planning add another type of action supported by Oozie (going by your example) or an engine that is parallel to Oozie. Either way, the design is extensible. > Adding custom engine in Apache Falcon > - > > Key: FALCON-2299 > URL: https://issues.apache.org/jira/browse/FALCON-2299 > Project: Falcon > Issue Type: Improvement > Components: general >Affects Versions: 0.9 >Reporter: Aniket Rajendra More > Labels: features > Fix For: 0.9 > > > Falcon currently supports 4 engines - oozie, pig, hive, spark. Is it possible > to configure Falcon to include another engine apart from the ones already > provided ? > We might be able to contribute to the Falcon project source code in order to > support custom engine. But is there any other way using which we can plug > custom engine to an existing Falcon build instead of creating our own Falcon > build which supports our engine ? > Has falcon opened its api for letting developers integrate their own > tools/engines ? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
