Re: Flume 1.7.0 release

[Saikat Kanjilal]

I would like to help out managing Jira's but never heard back from the 
community about the graph sink that I've been working on. Does it make sense to 
do a google hangout to discuss roadmap/upcoming features?

Sent from my iPhone

> On Jun 11, 2016, at 10:19 AM, Lior Zeno  wrote:
> 
> Let's first examine our JIRA issues. We have fixed issues with an empty
> fixVersion. In addition, we still have unresolved issues with
> fixVersion=v1.7.0. Let's deal with these first. I would do it myself, but I
> don't have the appropriate permissions for that.
> 
> On Sat, Jun 11, 2016 at 8:10 PM, Hari Shreedharan 
> wrote:
> 
>> Sound good to me. If we have a volunteer to run the release I will gladly
>> help out.
>>> On Sat, Jun 11, 2016 at 6:54 AM Lior Zeno  wrote:
>>> 
>>> Anybody?
>>> 
 On Thu, Jun 9, 2016 at 7:24 PM, Lior Zeno  wrote:
 
 Hi guys,
 
 I think we should work together towards a new release. It has been a
>> year
 since the last release, and there are many new features that were added
>>> in
 this year.
 What do you think?
 
 Lior
>> 

Re: Flume 1.7.0 release

[Lior Zeno]

Let's first examine our JIRA issues. We have fixed issues with an empty
fixVersion. In addition, we still have unresolved issues with
fixVersion=v1.7.0. Let's deal with these first. I would do it myself, but I
don't have the appropriate permissions for that.

On Sat, Jun 11, 2016 at 8:10 PM, Hari Shreedharan 
wrote:

> Sound good to me. If we have a volunteer to run the release I will gladly
> help out.
> On Sat, Jun 11, 2016 at 6:54 AM Lior Zeno  wrote:
>
> > Anybody?
> >
> > On Thu, Jun 9, 2016 at 7:24 PM, Lior Zeno  wrote:
> >
> > > Hi guys,
> > >
> > > I think we should work together towards a new release. It has been a
> year
> > > since the last release, and there are many new features that were added
> > in
> > > this year.
> > > What do you think?
> > >
> > > Lior
> > >
> >
>

Re: Flume 1.7.0 release

[Hari Shreedharan]

Sound good to me. If we have a volunteer to run the release I will gladly
help out.
On Sat, Jun 11, 2016 at 6:54 AM Lior Zeno  wrote:

> Anybody?
>
> On Thu, Jun 9, 2016 at 7:24 PM, Lior Zeno  wrote:
>
> > Hi guys,
> >
> > I think we should work together towards a new release. It has been a year
> > since the last release, and there are many new features that were added
> in
> > this year.
> > What do you think?
> >
> > Lior
> >
>

Enforce coding conventions at compilation time

[Lior Zeno]

Hi guys, we should make the reviewing process easier and more focused on
correctness rather than style issues. I suggest enforcing our code style (
https://cwiki.apache.org/confluence/display/FLUME/Code+Formatting) at
compile time using the maven checkstyle plugin (
https://maven.apache.org/plugins/maven-checkstyle-plugin/). This will make
the reviewing process easier, and will make sure that all committed code is
strictly following our code style.
What do you think?
Thanks

Dangling JIRA issues

[Lior Zeno]

Hi guys, there are many JIRA issues that are still open but are not
relevant anymore. We also have lots of unresolved issues with a submitted
patch linked to them, that we should review and commit or reject. We should
definitely reorganize our issues and discard old/irrelevant issues and
commit/reject issues with submitted patches.
Thanks

[jira] [Commented] (FLUME-2567) Remove unneeded repository declarations in pom.xml

[Lior Zeno (JIRA)]

[ 
https://issues.apache.org/jira/browse/FLUME-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325884#comment-15325884
 ] 

Lior Zeno commented on FLUME-2567:
--

Why hasn't this patch been committed?

> Remove unneeded repository declarations in pom.xml
> --
>
> Key: FLUME-2567
> URL: https://issues.apache.org/jira/browse/FLUME-2567
> Project: Flume
>  Issue Type: Bug
>Reporter: Santiago M. Mola
>Assignee: Santiago M. Mola
>Priority: Minor
> Attachments: FLUME-2567-0.patch
>
>
> pom.xml contains multiple repository declarations that do not seem to be 
> needed (jboss, maven central, cloudera). Actually, it seems to me that none 
> of these is needed.
> Can we remove all repository declarations and let it use just the default 
> (Maven Central)?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FLUME-2853) Allow for YAML configuration files

[Lior Zeno (JIRA)]

[ 
https://issues.apache.org/jira/browse/FLUME-2853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325880#comment-15325880
 ] 

Lior Zeno commented on FLUME-2853:
--

+1. Can I be assigned for this?

> Allow for YAML configuration files
> --
>
> Key: FLUME-2853
> URL: https://issues.apache.org/jira/browse/FLUME-2853
> Project: Flume
>  Issue Type: Improvement
>  Components: Configuration
>Reporter: Christopher White
>Priority: Minor
>
> Allow for YAML formatted configuration files 
> (http://www.yaml.org/spec/1.2/spec.html).
> This provides:
> * A more condensed format than properties files
> * Less 'typo' prone for repetitive common prefixes
> * Ability to define a value once and reuse via references (see [spec - 
> Structures - Example 2.10|http://www.yaml.org/spec/1.2/spec.html#id2760395]
> For example compare the following properties file and potential YAML 
> equivalent:
> {code:title=agent.properties}
> host1.sources = source1
> host1.channels = channel1
> host1.sinks = sink1
> host1.sources.source1.type = seq
> host1.sources.source1.channels = channel1
> host1.channels.channel1.type = memory
> host1.channels.channel1.capacity = 1
> host1.sinks.sink1.type = null
> host1.sinks.sink1.channel = channel1
> {code}
> {code:title=agent.yaml}
> host1:
>   sources:
> _: source1
> source1:
>   type: seq
>   channels: channel1
>   
>   channels:
> _: channel1
> channel1:
>   type: memory
>   capacity: 1
>   
>   sinks:
> _: sink1
> sink1:
>   type: null
>   channel: channel1
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FLUME-2494) ElasticSearchSink: Allow the ttl to be set from the header.

[Lior Zeno (JIRA)]

[ 
https://issues.apache.org/jira/browse/FLUME-2494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325878#comment-15325878
 ] 

Lior Zeno commented on FLUME-2494:
--

The _ttl field is deprecated since Elasticsearch 2.0 
(https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-ttl-field.html),
 I think we should remove it from the configuration and follow the suggestion 
of time-based rolling indices instead. 

> ElasticSearchSink: Allow the ttl to be set from the header.
> ---
>
> Key: FLUME-2494
> URL: https://issues.apache.org/jira/browse/FLUME-2494
> Project: Flume
>  Issue Type: Improvement
>  Components: Sinks+Sources
>Reporter: Susie Murphy
>Priority: Minor
>
> Currently the ttl of documents is set based on the ttl field in the config 
> file. It would be good if the ttl could be set by a field in the document's 
> header.
> This would allow for more flexibility, making it easier if you want different 
> ttls for different documents.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FLUME-1589) FlumeDeveloperGuide legacyThrift

[Lior Zeno (JIRA)]

[ 
https://issues.apache.org/jira/browse/FLUME-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325876#comment-15325876
 ] 

Lior Zeno commented on FLUME-1589:
--

This issue can be closed.

> FlumeDeveloperGuide legacyThrift
> 
>
> Key: FLUME-1589
> URL: https://issues.apache.org/jira/browse/FLUME-1589
> Project: Flume
>  Issue Type: Documentation
>  Components: Docs
>Reporter: Roy
>Priority: Trivial
>
> flume-ng-doc/sphinx/FlumeUserGuide.rst
> On line 351 & 366:
> org.apache.source.thriftLegacy.ThriftLegacySource
> Should be:
> org.apache.flume.source.thriftLegacy.ThriftLegacySource
> Will you guys accept pull requests on github for simple things like this?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FLUME-1592) Remove appendTimeout from HDFS sink docs

[Lior Zeno (JIRA)]

[ 
https://issues.apache.org/jira/browse/FLUME-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325875#comment-15325875
 ] 

Lior Zeno commented on FLUME-1592:
--

This issue can be closed

> Remove appendTimeout from HDFS sink docs
> 
>
> Key: FLUME-1592
> URL: https://issues.apache.org/jira/browse/FLUME-1592
> Project: Flume
>  Issue Type: Documentation
>Reporter: Mike Percy
>Assignee: Jeff Lord
>Priority: Trivial
>
> appendTimeout is no longer used



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Flume 1.7.0 release

[Lior Zeno]

Anybody?

On Thu, Jun 9, 2016 at 7:24 PM, Lior Zeno  wrote:

> Hi guys,
>
> I think we should work together towards a new release. It has been a year
> since the last release, and there are many new features that were added in
> this year.
> What do you think?
>
> Lior
>