Please propose a reasonable time. IMO, there is always something "almost
ready" to be committed that contributors will want to squeeze into a
release. The request to include something into a release should point to
an open PR, not to a JIRA. Everything else may be optionally included
into a rel
I think in absence of a fixed time release schedule it is actually
reasonable to allow for more than a week to discuss an upcoming release
with new features (not patch releases). This gives sufficient time for
contributors to react and possibly get their ducks in a row. I don't think
that there sho
[
https://issues.apache.org/jira/browse/APEXCORE-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15970240#comment-15970240
]
Vlad Rozov commented on APEXCORE-703:
-
Why not to have a state that indicates that a
I believe it should be standard Apache voting rules and timing policy.
When somebody propose a release and there is no objections (-1), once
voting is over, the RC can be cut and submitted for the vote. IMO, it is
reasonable to assume that "way ahead" is one week and not one month.
Thank you,
[
https://issues.apache.org/jira/browse/APEXCORE-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15970236#comment-15970236
]
Thomas Weise commented on APEXCORE-703:
---
Also, I believe we did not see this befor
[
https://issues.apache.org/jira/browse/APEXCORE-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15970234#comment-15970234
]
Thomas Weise commented on APEXCORE-703:
---
Vlad, thanks for checking. I don't think
[
https://issues.apache.org/jira/browse/APEXCORE-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15970233#comment-15970233
]
Vlad Rozov commented on APEXCORE-703:
-
[~thw] I don't see undeployed operators being
Hi Thomas,
I assume to have maximum generic implementation. The signatures of all
methods in the implementation will not contain anything log4j specific. And
if we decide to add an abstraction layer to the logger calls in Apex or to
use another logger implementation, it can be easily changed to su
There is a need for the community to agree on timing/scope of a release.
That discussion should take place way ahead of cutting it. It is
appropriate and desirable that folks think about and express their
preferences on what they would like to see as part of the next release.
It may be a priority
Hi Sergey,
What I'm asking is that the feature is implemented in a way that will allow
Apex to run with different logger backend. That means that log4j needs to
be optional.
Thanks,
Thomas
On Sat, Apr 15, 2017 at 2:01 PM, Sergey Golovko
wrote:
> I agree it would be very nice to use only slf4j
[
https://issues.apache.org/jira/browse/APEXCORE-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15970168#comment-15970168
]
ASF GitHub Bot commented on APEXCORE-704:
-
GitHub user sgolovko opened a pull re
GitHub user sgolovko opened a pull request:
https://github.com/apache/apex-core/pull/515
APEXCORE-704 Add supporting of programmatic logger appender
Implemented supporting of a programmatic logger appender that can be added
to Apex Application Master and Containers and be configurab
Sergey Golovko created APEXCORE-704:
---
Summary: Add supporting of programmatic logger appender
Key: APEXCORE-704
URL: https://issues.apache.org/jira/browse/APEXCORE-704
Project: Apache Apex Core
I agree it would be very nice to use only slf4j interfaces for the
implementation. But unfortunately the interface Appender belongs to
org.apache.log4j package.
"SLF4J is only a facade, meaning that it does not provide a complete
logging solution. Operations such as configuring appenders or settin
[
https://issues.apache.org/jira/browse/APEXCORE-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15970001#comment-15970001
]
Vlad Rozov commented on APEXCORE-699:
-
It will be good to have VersionInfo defined a
[
https://issues.apache.org/jira/browse/APEXCORE-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pramod Immaneni updated APEXCORE-246:
-
Fix Version/s: 3.4.0
> Add capability in the engine to let the operator know about the n
[
https://issues.apache.org/jira/browse/APEXCORE-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pramod Immaneni closed APEXCORE-246.
> Add capability in the engine to let the operator know about the next
> checkpoint window
>
[
https://issues.apache.org/jira/browse/APEXCORE-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pramod Immaneni resolved APEXCORE-360.
--
Resolution: Fixed
> Add capability in the engine to let the operator know about the ne
[
https://issues.apache.org/jira/browse/APEXCORE-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pramod Immaneni closed APEXCORE-360.
> Add capability in the engine to let the operator know about the next
> checkpoint window
>
[
https://issues.apache.org/jira/browse/APEXCORE-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pramod Immaneni reopened APEXCORE-360:
--
> Add capability in the engine to let the operator know about the next
> checkpoint windo
[
https://issues.apache.org/jira/browse/APEXCORE-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pramod Immaneni updated APEXCORE-360:
-
Fix Version/s: (was: 3.5.0)
3.4.0
> Add capability in the engine
[
https://issues.apache.org/jira/browse/APEXCORE-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pramod Immaneni updated APEXCORE-360:
-
Fix Version/s: 3.5.0
> Add capability in the engine to let the operator know about the n
[
https://issues.apache.org/jira/browse/APEXCORE-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pramod Immaneni closed APEXCORE-360.
> Add capability in the engine to let the operator know about the next
> checkpoint window
>
[
https://issues.apache.org/jira/browse/APEXCORE-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pramod Immaneni closed APEXCORE-460.
> Token refresh mechanism not considering keytab specified in command line
> -
[
https://issues.apache.org/jira/browse/APEXCORE-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pramod Immaneni updated APEXCORE-460:
-
Fix Version/s: 3.5.0
> Token refresh mechanism not considering keytab specified in comma
[
https://issues.apache.org/jira/browse/APEXCORE-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vlad Rozov closed APEXCORE-309.
---
> Site unable to update releases due to fetch-versions errors
>
[
https://issues.apache.org/jira/browse/APEXCORE-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vlad Rozov closed APEXCORE-311.
---
> Fix release date formatting
> ---
>
> Key: APEXCORE-311
>
[
https://issues.apache.org/jira/browse/APEXCORE-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vlad Rozov closed APEXCORE-388.
---
> Links to 3rd party pages should follow guidelines defined at
> http://www.apache.org/foundation/marks
[
https://issues.apache.org/jira/browse/APEXCORE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vlad Rozov resolved APEXCORE-316.
-
Resolution: Cannot Reproduce
Assignee: (was: Timothy Farkas)
Please reopen with reprod
[
https://issues.apache.org/jira/browse/APEXCORE-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vlad Rozov reassigned APEXCORE-123:
---
Assignee: (was: gaurav gupta)
> Node Locality doesn't work with CDH
> -
30 matches
Mail list logo
