[jira] [Assigned] (FALCON-2059) BacklogMetricEmitter Service for Falcon

[ https://issues.apache.org/jira/browse/FALCON-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pavan kumar kolamuri reassigned FALCON-2059: Assignee: pavan kumar kolamuri > BacklogMetricEmitter Service for Falcon

[jira] [Created] (FALCON-2059) BacklogMetricEmitter Service for Falcon

pavan kumar kolamuri created FALCON-2059: Summary: BacklogMetricEmitter Service for Falcon Key: FALCON-2059 URL: https://issues.apache.org/jira/browse/FALCON-2059 Project: Falcon

[jira] [Updated] (FALCON-1893) Add documentation and examples for spark workflow engine

[ https://issues.apache.org/jira/browse/FALCON-1893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pavan kumar kolamuri updated FALCON-1893: - Summary: Add documentation and examples for spark workflow engine (was: Add

[jira] [Updated] (FALCON-1893) Add documentation and examples for Spark workflow engine

[ https://issues.apache.org/jira/browse/FALCON-1893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pavan kumar kolamuri updated FALCON-1893: - Summary: Add documentation and examples for Spark workflow engine (was: Add

[jira] [Resolved] (FALCON-1935) Can't start Falcon with default startup.properties (FalconJPAService fails)

[ https://issues.apache.org/jira/browse/FALCON-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pavan kumar kolamuri resolved FALCON-1935. -- Resolution: Fixed Fix Version/s: trunk Issue resolved by pull request

[jira] [Resolved] (FALCON-1956) Graphite Plugin for monitoring

[ https://issues.apache.org/jira/browse/FALCON-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pavan kumar kolamuri resolved FALCON-1956. -- Resolution: Fixed Fix Version/s: trunk Issue resolved by pull request

[jira] [Created] (FALCON-1910) Optional Input should be truly optional in case of Native Scheduler as well

pavan kumar kolamuri created FALCON-1910: Summary: Optional Input should be truly optional in case of Native Scheduler as well Key: FALCON-1910 URL: https://issues.apache.org/jira/browse/FALCON-1910

[jira] [Commented] (FALCON-1867) hardcoded query names in JDBCStateStore

[ https://issues.apache.org/jira/browse/FALCON-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15215566#comment-15215566 ] pavan kumar kolamuri commented on FALCON-1867: -- [~ajayyadava] Make sense. [~Praveen] We are

[jira] [Commented] (FALCON-1867) hardcoded query names in JDBCStateStore

[ https://issues.apache.org/jira/browse/FALCON-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15214700#comment-15214700 ] pavan kumar kolamuri commented on FALCON-1867: -- [~Praveen] Can you explain what kind of run

[jira] [Commented] (FALCON-1817) Update xsd for Spark execution engine

[ https://issues.apache.org/jira/browse/FALCON-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15199394#comment-15199394 ] pavan kumar kolamuri commented on FALCON-1817: -- [~peeyushb] All this spark options are

[jira] [Commented] (FALCON-1406) Effective time in Entity updates.

[ https://issues.apache.org/jira/browse/FALCON-1406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15184631#comment-15184631 ] pavan kumar kolamuri commented on FALCON-1406: -- Just started review, had some initial

[jira] [Commented] (FALCON-1794) Behaviour mismatch in running Api when scheduled on native instead of oozie

[ https://issues.apache.org/jira/browse/FALCON-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15182819#comment-15182819 ] pavan kumar kolamuri commented on FALCON-1794: -- [~deepak.barr] Sure no problem Thanks for

[jira] [Commented] (FALCON-1794) Behaviour mismatch in running Api when scheduled on native instead of oozie

[ https://issues.apache.org/jira/browse/FALCON-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15182582#comment-15182582 ] pavan kumar kolamuri commented on FALCON-1794: -- [~deepak.barr] Can you please update patch

[jira] [Resolved] (FALCON-1825) Process end time inclusive in case of Native Scheduler

[ https://issues.apache.org/jira/browse/FALCON-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pavan kumar kolamuri resolved FALCON-1825. -- Resolution: Fixed Fix Version/s: trunk Issue resolved by pull request

[jira] [Commented] (FALCON-1845) Retries Stopped happening for all entities when one entity was deleted during rerun of instance

[ https://issues.apache.org/jira/browse/FALCON-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15179468#comment-15179468 ] pavan kumar kolamuri commented on FALCON-1845: -- There won't be any stack trace we are

[jira] [Comment Edited] (FALCON-1845) Retries Stopped happening for all entities when one entity was deleted during rerun of instance

[ https://issues.apache.org/jira/browse/FALCON-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15179468#comment-15179468 ] pavan kumar kolamuri edited comment on FALCON-1845 at 3/4/16 6:56 AM:

[jira] [Resolved] (FALCON-1826) Execution order not honoured when instances are KILLED

[ https://issues.apache.org/jira/browse/FALCON-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pavan kumar kolamuri resolved FALCON-1826. -- Resolution: Fixed Fix Version/s: trunk Issue resolved by pull request

[jira] [Commented] (FALCON-1826) Execution order not honoured when instances are KILLED

[ https://issues.apache.org/jira/browse/FALCON-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15179437#comment-15179437 ] pavan kumar kolamuri commented on FALCON-1826: -- +1 will commit shortly. > Execution order

[jira] [Created] (FALCON-1845) Retries Stopped happening for all entities when one entity was deleted during rerun of instance

pavan kumar kolamuri created FALCON-1845: Summary: Retries Stopped happening for all entities when one entity was deleted during rerun of instance Key: FALCON-1845 URL:

[jira] [Created] (FALCON-1825) Process end time not exclusive in case of Native Scheduler

pavan kumar kolamuri created FALCON-1825: Summary: Process end time not exclusive in case of Native Scheduler Key: FALCON-1825 URL: https://issues.apache.org/jira/browse/FALCON-1825 Project:

[jira] [Commented] (FALCON-1803) SkipDryRun and properties options are not taken care in case of Native Scheduler during Schedule

[ https://issues.apache.org/jira/browse/FALCON-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15136153#comment-15136153 ] pavan kumar kolamuri commented on FALCON-1803: -- [~Praveen] Did you start working on this ? I

[jira] [Commented] (FALCON-1795) Kill api does not kill waiting/ready instances

[ https://issues.apache.org/jira/browse/FALCON-1795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15131907#comment-15131907 ] pavan kumar kolamuri commented on FALCON-1795: -- +1 for the patch. Will commit it if there

[jira] [Commented] (FALCON-1795) Kill api does not kill waiting/ready instances

[ https://issues.apache.org/jira/browse/FALCON-1795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15131947#comment-15131947 ] pavan kumar kolamuri commented on FALCON-1795: -- [~ajayyadava] Sometimes during review we

[jira] [Commented] (FALCON-1795) Kill api does not kill waiting/ready instances

[ https://issues.apache.org/jira/browse/FALCON-1795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15131908#comment-15131908 ] pavan kumar kolamuri commented on FALCON-1795: -- [~sandeep.samudrala] Please attach patch

[jira] [Created] (FALCON-1798) Evaluation of input paths and check for their availability in case of Native Scheduler

pavan kumar kolamuri created FALCON-1798: Summary: Evaluation of input paths and check for their availability in case of Native Scheduler Key: FALCON-1798 URL:

[jira] [Created] (FALCON-1803) SkipDryRun and properties options are not taken care in case of Native Scheduler during Schedule

pavan kumar kolamuri created FALCON-1803: Summary: SkipDryRun and properties options are not taken care in case of Native Scheduler during Schedule Key: FALCON-1803 URL:

[jira] [Commented] (FALCON-1435) EL Expression Evaluation of Entities in case of Native Scheduler

[ https://issues.apache.org/jira/browse/FALCON-1435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15125813#comment-15125813 ] pavan kumar kolamuri commented on FALCON-1435: -- Refactoring of

[jira] [Updated] (FALCON-1798) Evaluation of input paths and check for their availability in case of Native Scheduler

[ https://issues.apache.org/jira/browse/FALCON-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pavan kumar kolamuri updated FALCON-1798: - Attachment: FALCON-1798-initial.patch > Evaluation of input paths and check for

[jira] [Created] (FALCON-1802) Workflow Builder for scheduling based on Data for Process in case of Native Scheduler

pavan kumar kolamuri created FALCON-1802: Summary: Workflow Builder for scheduling based on Data for Process in case of Native Scheduler Key: FALCON-1802 URL:

[jira] [Commented] (FALCON-1774) Falcon to honour PRISM_URL env var

[ https://issues.apache.org/jira/browse/FALCON-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15123408#comment-15123408 ] pavan kumar kolamuri commented on FALCON-1774: -- [~ajayyadava] Why to add API just to say

[jira] [Commented] (FALCON-1778) Check licenses and copyright information

[ https://issues.apache.org/jira/browse/FALCON-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15123180#comment-15123180 ] pavan kumar kolamuri commented on FALCON-1778: -- +1 looks good > Check licenses and

[jira] [Commented] (FALCON-1774) Falcon to honour PRISM_URL env var

[ https://issues.apache.org/jira/browse/FALCON-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121006#comment-15121006 ] pavan kumar kolamuri commented on FALCON-1774: -- [~Praveen] Did u try to search any other

[jira] [Commented] (FALCON-1778) Check licenses and copyright information

[ https://issues.apache.org/jira/browse/FALCON-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121016#comment-15121016 ] pavan kumar kolamuri commented on FALCON-1778: -- Thanks [~pallavi.rao] small question : We

[jira] [Commented] (FALCON-1787) Ooozie pig-action.xml requires hive sharelib for HCatalog use

[ https://issues.apache.org/jira/browse/FALCON-1787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15122992#comment-15122992 ] pavan kumar kolamuri commented on FALCON-1787: -- +1 Looks Good > Ooozie pig-action.xml

[jira] [Commented] (FALCON-1609) Add entity commands to falcon spring-shell CLI

[ https://issues.apache.org/jira/browse/FALCON-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15120836#comment-15120836 ] pavan kumar kolamuri commented on FALCON-1609: -- Thanks [~prongs] will look into it. > Add

[jira] [Commented] (FALCON-1609) Add entity commands to falcon spring-shell CLI

[ https://issues.apache.org/jira/browse/FALCON-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15119861#comment-15119861 ] pavan kumar kolamuri commented on FALCON-1609: -- [~prongs] Thanks for working on this. Can

[jira] [Commented] (FALCON-1778) Check licenses and copyright information

[ https://issues.apache.org/jira/browse/FALCON-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15119231#comment-15119231 ] pavan kumar kolamuri commented on FALCON-1778: -- [~pallavi.rao] I think with deepak's patch

[jira] [Commented] (FALCON-1548) Refactoring for Instance Execution operations in Native Scheduler

[ https://issues.apache.org/jira/browse/FALCON-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15114949#comment-15114949 ] pavan kumar kolamuri commented on FALCON-1548: -- [~Praveen] Assigned to you. Thanks for

[jira] [Updated] (FALCON-1548) Refactoring for Instance Execution operations in Native Scheduler

[ https://issues.apache.org/jira/browse/FALCON-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pavan kumar kolamuri updated FALCON-1548: - Assignee: Praveen Adlakha (was: pavan kumar kolamuri) > Refactoring for

[jira] [Updated] (FALCON-1758) APIs fail when oozie workflow entries are deleted

[ https://issues.apache.org/jira/browse/FALCON-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pavan kumar kolamuri updated FALCON-1758: - Attachment: FALCON-1758.patch > APIs fail when oozie workflow entries are

[jira] [Commented] (FALCON-1758) APIs fail when oozie workflow entries are deleted

[ https://issues.apache.org/jira/browse/FALCON-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15114218#comment-15114218 ] pavan kumar kolamuri commented on FALCON-1758: -- After an offline discussion with

[jira] [Commented] (FALCON-1716) API fails with CommunicationsException when mysql interaction time is longer than 53,434,939 milliseconds

[ https://issues.apache.org/jira/browse/FALCON-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15112277#comment-15112277 ] pavan kumar kolamuri commented on FALCON-1716: -- Updated the patch please review

[jira] [Commented] (FALCON-1664) Add Postgres support for native scheduler

[ https://issues.apache.org/jira/browse/FALCON-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15110488#comment-15110488 ] pavan kumar kolamuri commented on FALCON-1664: -- +1 for the patch > Add Postgres support for

[jira] [Updated] (FALCON-1757) EntityNotRegisteredException when entity is deleted from falcon

[ https://issues.apache.org/jira/browse/FALCON-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pavan kumar kolamuri updated FALCON-1757: - Attachment: FALCON-1757.patch > EntityNotRegisteredException when entity is

[jira] [Commented] (FALCON-1757) EntityNotRegisteredException when entity is deleted from falcon

[ https://issues.apache.org/jira/browse/FALCON-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15110237#comment-15110237 ] pavan kumar kolamuri commented on FALCON-1757: -- By the time falcon get failure notifications

[jira] [Commented] (FALCON-1682) Falcon server starts successfully even if application services fail to start

[ https://issues.apache.org/jira/browse/FALCON-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15106426#comment-15106426 ] pavan kumar kolamuri commented on FALCON-1682: -- Looks like it's not a small change to change

[jira] [Created] (FALCON-1760) Upgrade jetty version and fix Falcon start issue while Application initialization fails

pavan kumar kolamuri created FALCON-1760: Summary: Upgrade jetty version and fix Falcon start issue while Application initialization fails Key: FALCON-1760 URL:

[jira] [Commented] (FALCON-1716) API fails with CommunicationsException when mysql interaction time is longer than 53,434,939 milliseconds

[ https://issues.apache.org/jira/browse/FALCON-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15106715#comment-15106715 ] pavan kumar kolamuri commented on FALCON-1716: -- In Connection Pool of JDBC, there are pool

[jira] [Commented] (FALCON-1723) Rerun with skip fail actions won't work in few cases

[ https://issues.apache.org/jira/browse/FALCON-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15106719#comment-15106719 ] pavan kumar kolamuri commented on FALCON-1723: -- [~pallavi.rao] Can you try re-basing now. >

[jira] [Updated] (FALCON-1716) API fails with CommunicationsException when mysql interaction time is longer than 53,434,939 milliseconds

[ https://issues.apache.org/jira/browse/FALCON-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pavan kumar kolamuri updated FALCON-1716: - Attachment: FALCON-1716.patch > API fails with CommunicationsException when

[jira] [Commented] (FALCON-1716) API fails with CommunicationsException when mysql interaction time is longer than 53,434,939 milliseconds

[ https://issues.apache.org/jira/browse/FALCON-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1510#comment-1510 ] pavan kumar kolamuri commented on FALCON-1716: -- I am not putting this on review board since

[jira] [Updated] (FALCON-1723) Rerun with skip fail actions won't work in few cases

[ https://issues.apache.org/jira/browse/FALCON-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pavan kumar kolamuri updated FALCON-1723: - Attachment: FALCON-1723-v2.patch > Rerun with skip fail actions won't work in

[jira] [Commented] (FALCON-1716) API fails with CommunicationsException when mysql interaction time is longer than 53,434,939 milliseconds

[ https://issues.apache.org/jira/browse/FALCON-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15106665#comment-15106665 ] pavan kumar kolamuri commented on FALCON-1716: -- Because of wrong default value of

[jira] [Commented] (FALCON-1723) Rerun with skip fail actions won't work in few cases

[ https://issues.apache.org/jira/browse/FALCON-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15106816#comment-15106816 ] pavan kumar kolamuri commented on FALCON-1723: -- I have submit patch for 0.9 branch. Please

[jira] [Updated] (FALCON-1723) Rerun with skip fail actions won't work in few cases

[ https://issues.apache.org/jira/browse/FALCON-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pavan kumar kolamuri updated FALCON-1723: - Attachment: FALCON-1723-0.9-branch.patch > Rerun with skip fail actions won't

[jira] [Assigned] (FALCON-1758) APIs fail when oozie workflow entries are deleted

[ https://issues.apache.org/jira/browse/FALCON-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pavan kumar kolamuri reassigned FALCON-1758: Assignee: pavan kumar kolamuri > APIs fail when oozie workflow entries

[jira] [Commented] (FALCON-1758) APIs fail when oozie workflow entries are deleted

[ https://issues.apache.org/jira/browse/FALCON-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15107003#comment-15107003 ] pavan kumar kolamuri commented on FALCON-1758: -- [~pragya.mittal] Looks like stacktrace

[jira] [Assigned] (FALCON-1757) EntityNotRegisteredException when entity is deleted from falcon

[ https://issues.apache.org/jira/browse/FALCON-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pavan kumar kolamuri reassigned FALCON-1757: Assignee: pavan kumar kolamuri > EntityNotRegisteredException when entity

[jira] [Commented] (FALCON-1682) Falcon server starts successfully even if application services fail to start

[ https://issues.apache.org/jira/browse/FALCON-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15105407#comment-15105407 ] pavan kumar kolamuri commented on FALCON-1682: -- I have explored about them we need to bump

[jira] [Updated] (FALCON-1723) Rerun with skip fail actions won't work in few cases

[ https://issues.apache.org/jira/browse/FALCON-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pavan kumar kolamuri updated FALCON-1723: - Attachment: FALCON-1723-v1.patch > Rerun with skip fail actions won't work in

[jira] [Commented] (FALCON-1682) Falcon server starts successfully even if application services fail to start

[ https://issues.apache.org/jira/browse/FALCON-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15106297#comment-15106297 ] pavan kumar kolamuri commented on FALCON-1682: -- Even i agree same, i will go ahead and

[jira] [Commented] (FALCON-1723) Rerun with skip fail actions won't work in few cases

[ https://issues.apache.org/jira/browse/FALCON-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15106301#comment-15106301 ] pavan kumar kolamuri commented on FALCON-1723: -- Added doc regarding prioritization over

[jira] [Commented] (FALCON-1538) Prism status gives wrong info.

[ https://issues.apache.org/jira/browse/FALCON-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15103132#comment-15103132 ] pavan kumar kolamuri commented on FALCON-1538: -- [~Praveen] Can you please paste result how

[jira] [Commented] (FALCON-1662) Ensure entity can be scheduled on multiple clusters on same colo

[ https://issues.apache.org/jira/browse/FALCON-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15103149#comment-15103149 ] pavan kumar kolamuri commented on FALCON-1662: -- +1 for the patch > Ensure entity can be

[jira] [Commented] (FALCON-1715) IllegalStateException in MetadataMappingService when entity is scheduled via native scheduler

[ https://issues.apache.org/jira/browse/FALCON-1715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15097914#comment-15097914 ] pavan kumar kolamuri commented on FALCON-1715: -- +1 looks good > IllegalStateException in

[jira] [Updated] (FALCON-1723) Rerun with skip fail actions won't work in few cases

[ https://issues.apache.org/jira/browse/FALCON-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pavan kumar kolamuri updated FALCON-1723: - Attachment: FALCON-1723.patch > Rerun with skip fail actions won't work in few

[jira] [Commented] (FALCON-1741) Rerun API behaviour different in case of succeeded instances

[ https://issues.apache.org/jira/browse/FALCON-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15091663#comment-15091663 ] pavan kumar kolamuri commented on FALCON-1741: -- +1 for the patch. > Rerun API behaviour

[jira] [Commented] (FALCON-1230) Data based notification Service to notify execution instances when data becomes available

[ https://issues.apache.org/jira/browse/FALCON-1230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15091706#comment-15091706 ] pavan kumar kolamuri commented on FALCON-1230: -- Thanks [~pallavi.rao] [~ajayyadava] for

[jira] [Commented] (FALCON-1601) Make Falcon StateStore more secure by not disclosing imp params in startup.props

[ https://issues.apache.org/jira/browse/FALCON-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15091710#comment-15091710 ] pavan kumar kolamuri commented on FALCON-1601: -- Thanks [~pallavi.rao] [~ajayyadava] for

[jira] [Assigned] (FALCON-1716) API fails with CommunicationsException when mysql interaction time is longer than 53,434,939 milliseconds

[ https://issues.apache.org/jira/browse/FALCON-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pavan kumar kolamuri reassigned FALCON-1716: Assignee: pavan kumar kolamuri > API fails with CommunicationsException

[jira] [Updated] (FALCON-1715) IllegalStateException in MetadataMappingService when entity is scheduled via native scheduler

[ https://issues.apache.org/jira/browse/FALCON-1715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pavan kumar kolamuri updated FALCON-1715: - Assignee: Pallavi Rao > IllegalStateException in MetadataMappingService when

[jira] [Updated] (FALCON-1682) Falcon server starts successfully even if mysql db is not created.

[ https://issues.apache.org/jira/browse/FALCON-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pavan kumar kolamuri updated FALCON-1682: - Attachment: FALCON-1682.patch > Falcon server starts successfully even if mysql

[jira] [Commented] (FALCON-1682) Falcon server starts successfully even if mysql db is not created.

[ https://issues.apache.org/jira/browse/FALCON-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15091847#comment-15091847 ] pavan kumar kolamuri commented on FALCON-1682: -- Based on discussion with [~pallavi.rao], i

[jira] [Commented] (FALCON-1678) SLA Monitoring does not honour entity end date

[ https://issues.apache.org/jira/browse/FALCON-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15091450#comment-15091450 ] pavan kumar kolamuri commented on FALCON-1678: -- +1 for the patch > SLA Monitoring does not

[jira] [Updated] (FALCON-1230) Data based notification Service to notify execution instances when data becomes available

[ https://issues.apache.org/jira/browse/FALCON-1230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pavan kumar kolamuri updated FALCON-1230: - Attachment: FALCON-1230-v8.patch > Data based notification Service to notify

[jira] [Commented] (FALCON-1230) Data based notification Service to notify execution instances when data becomes available

[ https://issues.apache.org/jira/browse/FALCON-1230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15091541#comment-15091541 ] pavan kumar kolamuri commented on FALCON-1230: -- [~ajayyadava] Addressed your comments

[jira] [Commented] (FALCON-1230) Data based notification Service to notify execution instances when data becomes available

[ https://issues.apache.org/jira/browse/FALCON-1230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15088902#comment-15088902 ] pavan kumar kolamuri commented on FALCON-1230: -- I refactored most of things in next patch

[jira] [Commented] (FALCON-1677) Support re-tries for timed-out instances

[ https://issues.apache.org/jira/browse/FALCON-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15089016#comment-15089016 ] pavan kumar kolamuri commented on FALCON-1677: -- Completely agree with [~pallavi.rao] +1 for

[jira] [Commented] (FALCON-1230) Data based notification Service to notify execution instances when data becomes available

[ https://issues.apache.org/jira/browse/FALCON-1230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15089139#comment-15089139 ] pavan kumar kolamuri commented on FALCON-1230: -- [~ajayyadava] Please review now, i have

[jira] [Commented] (FALCON-1230) Data based notification Service to notify execution instances when data becomes available

[ https://issues.apache.org/jira/browse/FALCON-1230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15089137#comment-15089137 ] pavan kumar kolamuri commented on FALCON-1230: -- Raised

[jira] [Created] (FALCON-1738) Support Retry for failure Data-based Notifications and fix timeout test case in FalconExecutionServiceTest

pavan kumar kolamuri created FALCON-1738: Summary: Support Retry for failure Data-based Notifications and fix timeout test case in FalconExecutionServiceTest Key: FALCON-1738 URL:

[jira] [Updated] (FALCON-1230) Data based notification Service to notify execution instances when data becomes available

[ https://issues.apache.org/jira/browse/FALCON-1230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pavan kumar kolamuri updated FALCON-1230: - Attachment: FALCON-1230-v7.patch > Data based notification Service to notify

[jira] [Updated] (FALCON-1230) Data based notification Service to notify execution instances when data becomes available

[ https://issues.apache.org/jira/browse/FALCON-1230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pavan kumar kolamuri updated FALCON-1230: - Attachment: FALCON-1230-v6.patch > Data based notification Service to notify

[jira] [Commented] (FALCON-1230) Data based notification Service to notify execution instances when data becomes available

[ https://issues.apache.org/jira/browse/FALCON-1230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15087276#comment-15087276 ] pavan kumar kolamuri commented on FALCON-1230: -- I will refactor DataNotificationRequest

[jira] [Commented] (FALCON-1728) Process entity definition allows multiple clusters when it has output Feed defined.

[ https://issues.apache.org/jira/browse/FALCON-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15088724#comment-15088724 ] pavan kumar kolamuri commented on FALCON-1728: -- Yes [~bvellanki] you are right . Falcon

[jira] [Commented] (FALCON-1720) Rerun API does not rerun succeeded instances

[ https://issues.apache.org/jira/browse/FALCON-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15085359#comment-15085359 ] pavan kumar kolamuri commented on FALCON-1720: -- Thanks [~pragya.mittal] for raising the jira

[jira] [Commented] (FALCON-1230) Data based notification Service to notify execution instances when data becomes available

[ https://issues.apache.org/jira/browse/FALCON-1230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15085269#comment-15085269 ] pavan kumar kolamuri commented on FALCON-1230: -- Please review , my other patches blocked on

[jira] [Updated] (FALCON-1601) Make Falcon StateStore more secure by not disclosing imp params in startup.props

[ https://issues.apache.org/jira/browse/FALCON-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pavan kumar kolamuri updated FALCON-1601: - Attachment: FALCON-1601-v1.patch > Make Falcon StateStore more secure by not

[jira] [Commented] (FALCON-1601) Make Falcon StateStore more secure by not disclosing imp params in startup.props

[ https://issues.apache.org/jira/browse/FALCON-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15085261#comment-15085261 ] pavan kumar kolamuri commented on FALCON-1601: -- I have addressed comments based on

[jira] [Commented] (FALCON-1720) Rerun API does not rerun succeeded instances

[ https://issues.apache.org/jira/browse/FALCON-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15085356#comment-15085356 ] pavan kumar kolamuri commented on FALCON-1720: -- Thanks [~pallavi.rao] [~pragya.mittal]

[jira] [Commented] (FALCON-1725) Falcon API shows results in ascending order in native scheduler

[ https://issues.apache.org/jira/browse/FALCON-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15085321#comment-15085321 ] pavan kumar kolamuri commented on FALCON-1725: -- Just had minor nit in review board . Patch

[jira] [Commented] (FALCON-1682) Falcon server starts successfully even if mysql db is not created.

[ https://issues.apache.org/jira/browse/FALCON-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15085641#comment-15085641 ] pavan kumar kolamuri commented on FALCON-1682: -- [~pallavi.rao] [~sandeep.samudrala] I have

[jira] [Commented] (FALCON-1728) Process entity definition allows multiple clusters when it has output Feed defined.

[ https://issues.apache.org/jira/browse/FALCON-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15086815#comment-15086815 ] pavan kumar kolamuri commented on FALCON-1728: -- Just adding more points to what

[jira] [Commented] (FALCON-1682) Falcon server starts successfully even if mysql db is not created.

[ https://issues.apache.org/jira/browse/FALCON-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15086969#comment-15086969 ] pavan kumar kolamuri commented on FALCON-1682: -- Even i will prefer option-2 will look into

[jira] [Commented] (FALCON-1719) Retry does not update the state of the instance in the database

[ https://issues.apache.org/jira/browse/FALCON-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15086955#comment-15086955 ] pavan kumar kolamuri commented on FALCON-1719: -- [~sowmyaramesh] [~bvellanki] Thanks for

[jira] [Commented] (FALCON-1720) Rerun API does not rerun succeeded instances

[ https://issues.apache.org/jira/browse/FALCON-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15082678#comment-15082678 ] pavan kumar kolamuri commented on FALCON-1720: -- I am explaining all cases here Normal Rerun

[jira] [Updated] (FALCON-1720) Rerun API does not rerun succeeded instances

[ https://issues.apache.org/jira/browse/FALCON-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pavan kumar kolamuri updated FALCON-1720: - Attachment: FALCON-1720.patch > Rerun API does not rerun succeeded instances >

[jira] [Created] (FALCON-1723) Rerun with skip fail actions won't work in few cases

pavan kumar kolamuri created FALCON-1723: Summary: Rerun with skip fail actions won't work in few cases Key: FALCON-1723 URL: https://issues.apache.org/jira/browse/FALCON-1723 Project: Falcon

[jira] [Assigned] (FALCON-1723) Rerun with skip fail actions won't work in few cases

[ https://issues.apache.org/jira/browse/FALCON-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pavan kumar kolamuri reassigned FALCON-1723: Assignee: pavan kumar kolamuri > Rerun with skip fail actions won't work

[jira] [Commented] (FALCON-1720) Rerun API does not rerun succeeded instances

[ https://issues.apache.org/jira/browse/FALCON-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15082769#comment-15082769 ] pavan kumar kolamuri commented on FALCON-1720: -- All the four cases mentioned here are fixed

  1   2   3   4   5   >