[jira] [Resolved] (FLUME-1185) Images of FlumeDeveloperGuide and FlumeUserGuide can NOT be displayed in Chrome browser since wrong image paths

[ https://issues.apache.org/jira/browse/FLUME-1185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Paliwal resolved FLUME-1185. --- Resolution: Cannot Reproduce Fix Version/s: v1.5.0 Not able to find the mentioned issu

Review Request 16151: Patch for FLUME-2006 - in Avro the batch size is called batch-size, in all other sources batchSize

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/16151/ --- Review request for Flume. Bugs: FLUME-2006 https://issues.apache.org/jira/b

[jira] [Updated] (FLUME-2006) in Avro the batch size is called batch-size, in all other sources batchSize

[ https://issues.apache.org/jira/browse/FLUME-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Paliwal updated FLUME-2006: -- Attachment: FLUME-2006-0.patch > in Avro the batch size is called batch-size, in all other sour

[jira] [Updated] (FLUME-1501) Flume Scribe Source needs unit tests.

[ https://issues.apache.org/jira/browse/FLUME-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Paliwal updated FLUME-1501: -- Attachment: FLUME-1501-1.patch Rebased the patch against trunk. No changes done to the code. Ex

[jira] [Commented] (FLUME-1501) Flume Scribe Source needs unit tests.

[ https://issues.apache.org/jira/browse/FLUME-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843942#comment-13843942 ] Ashish Paliwal commented on FLUME-1501: --- Trying to find where I kept the patch, shal

[jira] [Commented] (FLUME-2243) AvroSource to use TransceiverThreadFactory for Thread naming while initializing NioServerSocketChannelFactory

[ https://issues.apache.org/jira/browse/FLUME-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843940#comment-13843940 ] Ashish Paliwal commented on FLUME-2243: --- [~hshreedharan] This is not committed. FLUM

[jira] [Commented] (FLUME-1501) Flume Scribe Source needs unit tests.

[ https://issues.apache.org/jira/browse/FLUME-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843929#comment-13843929 ] Ashish Paliwal commented on FLUME-1501: --- yeah, it's an old one. I shall rebase it. D

[jira] [Commented] (FLUME-1501) Flume Scribe Source needs unit tests.

[ https://issues.apache.org/jira/browse/FLUME-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843924#comment-13843924 ] Hari Shreedharan commented on FLUME-1501: - This patch does not seem to apply. Can

[jira] [Commented] (FLUME-2243) AvroSource to use TransceiverThreadFactory for Thread naming while initializing NioServerSocketChannelFactory

[ https://issues.apache.org/jira/browse/FLUME-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843920#comment-13843920 ] Hari Shreedharan commented on FLUME-2243: - [~ashishpaliwal] - Please confirm this

[jira] [Commented] (FLUME-2209) AsyncHBaseSink will never recover if the column family does not exists for the first start

[ https://issues.apache.org/jira/browse/FLUME-2209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843915#comment-13843915 ] Hari Shreedharan commented on FLUME-2209: - +1. Looks good. Committing. > AsyncHBa

[jira] [Updated] (FLUME-2262) Log4j Appender should use timeStamp field not getTimestamp

[ https://issues.apache.org/jira/browse/FLUME-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Jarcec Cecho updated FLUME-2262: -- Fix Version/s: v1.5.0 > Log4j Appender should use timeStamp field not getTimestamp > --

[jira] [Created] (FLUME-2263) Bump Hadoop 2 version to 2.2.0

Hari Shreedharan created FLUME-2263: --- Summary: Bump Hadoop 2 version to 2.2.0 Key: FLUME-2263 URL: https://issues.apache.org/jira/browse/FLUME-2263 Project: Flume Issue Type: Bug

[jira] [Commented] (FLUME-2130) Handle larger payloads via SyslogUDPSource

[ https://issues.apache.org/jira/browse/FLUME-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843903#comment-13843903 ] Ashish Paliwal commented on FLUME-2130: --- Hi Hari, Let me rework the patch and put i

Re: Review Request 16031: Patch for FLUME-2209

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/16031/#review30072 --- Ship it! Ship It! - Hari Shreedharan On Dec. 5, 2013, 1:57 a.m.,

[jira] [Commented] (FLUME-2130) Handle larger payloads via SyslogUDPSource

[ https://issues.apache.org/jira/browse/FLUME-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843896#comment-13843896 ] Hari Shreedharan commented on FLUME-2130: - Hi Ashish, Thanks for the patch. I hav

[jira] [Commented] (FLUME-2262) Log4j Appender should use timeStamp field not getTimestamp

[ https://issues.apache.org/jira/browse/FLUME-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843886#comment-13843886 ] Brock Noland commented on FLUME-2262: - Thank you! > Log4j Appender should use timeSta

[jira] [Updated] (FLUME-2262) Log4j Appender should use timeStamp field not getTimestamp

[ https://issues.apache.org/jira/browse/FLUME-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brock Noland updated FLUME-2262: Description: getTimestamp was added in log4j 1.2.15, we should use the timestamp field instead: 1

[jira] [Updated] (FLUME-2006) in Avro the batch size is called batch-size, in all other sources batchSize

[ https://issues.apache.org/jira/browse/FLUME-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Lord updated FLUME-2006: - Assignee: Ashish Paliwal (was: Jeff Lord) > in Avro the batch size is called batch-size, in all other so

[jira] [Commented] (FLUME-1227) Introduce some sort of SpillableChannel

[ https://issues.apache.org/jira/browse/FLUME-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843789#comment-13843789 ] Hari Shreedharan commented on FLUME-1227: - Yes, it was v7. > Introduce some sort

[jira] [Commented] (FLUME-1227) Introduce some sort of SpillableChannel

[ https://issues.apache.org/jira/browse/FLUME-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843787#comment-13843787 ] Roshan Naik commented on FLUME-1227: - will fix the 80 character length issue you note

[jira] [Commented] (FLUME-2243) AvroSource to use TransceiverThreadFactory for Thread naming while initializing NioServerSocketChannelFactory

[ https://issues.apache.org/jira/browse/FLUME-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843770#comment-13843770 ] Hari Shreedharan commented on FLUME-2243: - This one got committed with FLUME-2238.

Re: Review Request 15163: FLUME-2217 Preserve priority, timestamp and hostname fields in MultiportSyslogTcp, SyslogTcp and Udp sources

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/15163/ --- (Updated Dec. 10, 2013, 12:23 a.m.) Review request for Flume, Hari Shreedharan

Re: Review Request 15163: FLUME-2217 Preserve priority, timestamp and hostname fields in MultiportSyslogTcp, SyslogTcp and Udp sources

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/15163/ --- (Updated Dec. 9, 2013, 11:53 p.m.) Review request for Flume, Hari Shreedharan a

[jira] [Commented] (FLUME-2238) Provide option to configure worker threads in NettyAvroRpcClient

[ https://issues.apache.org/jira/browse/FLUME-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843702#comment-13843702 ] Hari Shreedharan commented on FLUME-2238: - +1. I am running the tests now, will co

Re: Review Request 15683: FLUME-2238 - Provide option to configure worker threads in NettyAvroRpcClient

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/15683/#review30060 --- Ship it! Ship It! - Hari Shreedharan On Nov. 21, 2013, 8:13 p.m.

Re: Review Request 15163: FLUME-2217 Preserve priority, timestamp and hostname fields in MultiportSyslogTcp, SyslogTcp and Udp sources

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/15163/ --- (Updated Dec. 9, 2013, 11:04 p.m.) Review request for Flume, Hari Shreedharan a

Re: Review Request 15163: FLUME-2217 Preserve priority, timestamp and hostname fields in MultiportSyslogTcp, SyslogTcp and Udp sources

> On Dec. 4, 2013, 3:39 a.m., Mike Percy wrote: > > flume-ng-core/src/test/java/org/apache/flume/source/TestSyslogParser.java, > > line 80 > > > > > > This is actually a really good test. Can you please loop twice, onc

[jira] [Commented] (FLUME-2262) Log4j Appender should use timeStamp field not getTimestamp

[ https://issues.apache.org/jira/browse/FLUME-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843616#comment-13843616 ] Hari Shreedharan commented on FLUME-2262: - +1. Looks good. Running tests and commi

[jira] [Assigned] (FLUME-2262) Log4j Appender should use timeStamp field not getTimestamp

[ https://issues.apache.org/jira/browse/FLUME-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brock Noland reassigned FLUME-2262: --- Assignee: Brock Noland > Log4j Appender should use timeStamp field not getTimestamp > ---

[jira] [Updated] (FLUME-2262) Log4j Appender should use timeStamp field not getTimestamp

[ https://issues.apache.org/jira/browse/FLUME-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brock Noland updated FLUME-2262: Attachment: FLUME-2262.patch > Log4j Appender should use timeStamp field not getTimestamp > ---

[jira] [Created] (FLUME-2262) Log4j Appender should use timeStamp field not getTimestamp

Brock Noland created FLUME-2262: --- Summary: Log4j Appender should use timeStamp field not getTimestamp Key: FLUME-2262 URL: https://issues.apache.org/jira/browse/FLUME-2262 Project: Flume Issue

[jira] [Commented] (FLUME-1227) Introduce some sort of SpillableChannel

[ https://issues.apache.org/jira/browse/FLUME-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843442#comment-13843442 ] Hari Shreedharan commented on FLUME-1227: - The patch seems to be failing tests : {

[jira] [Commented] (FLUME-1227) Introduce some sort of SpillableChannel

[ https://issues.apache.org/jira/browse/FLUME-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843421#comment-13843421 ] Hari Shreedharan commented on FLUME-1227: - Also, there are several lines > 80 char

[jira] [Commented] (FLUME-2261) Flume HDFS sinks can't overcome NN HA switching

[ https://issues.apache.org/jira/browse/FLUME-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843412#comment-13843412 ] Sergey commented on FLUME-2261: --- I didn't find any WARN/ERROR for the whole HDFS service on

[jira] [Commented] (FLUME-2261) Flume HDFS sinks can't overcome NN HA switching

[ https://issues.apache.org/jira/browse/FLUME-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843405#comment-13843405 ] Hari Shreedharan commented on FLUME-2261: - Does this not recover after your HDFS i

[jira] [Commented] (FLUME-1227) Introduce some sort of SpillableChannel

[ https://issues.apache.org/jira/browse/FLUME-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843403#comment-13843403 ] Hari Shreedharan commented on FLUME-1227: - Hi Roshan, In the takePrimary and take

[jira] [Commented] (FLUME-2228) HDFS namenode failover cause flume error

[ https://issues.apache.org/jira/browse/FLUME-2228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843390#comment-13843390 ] Sergey commented on FLUME-2228: --- I'm so sad to hear it. Thanks. > HDFS namenode failover ca

[jira] [Commented] (FLUME-2228) HDFS namenode failover cause flume error

[ https://issues.apache.org/jira/browse/FLUME-2228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843388#comment-13843388 ] Hari Shreedharan commented on FLUME-2228: - Typically, the only thing you can do is

[jira] [Created] (FLUME-2261) Flume HDFS sinks can't overcome NN HA switching

Sergey created FLUME-2261: - Summary: Flume HDFS sinks can't overcome NN HA switching Key: FLUME-2261 URL: https://issues.apache.org/jira/browse/FLUME-2261 Project: Flume Issue Type: Bug Com

Re: Patch Review Help needed

Thanks Hari ! On Mon, Dec 9, 2013 at 9:03 PM, Hari Shreedharan wrote: > I will take a look at a few of these today. Thanks got your patches Ashish! > > On Sunday, December 8, 2013, Ashish wrote: > > > Folks, > > > > Need help in reviewing the following patches. > > > > FLUME-2243 - AvroSource to

[jira] [Commented] (FLUME-2130) Handle larger payloads via SyslogUDPSource

[ https://issues.apache.org/jira/browse/FLUME-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843260#comment-13843260 ] Gopinathan A commented on FLUME-2130: - +1 for patch > Handle larger payloads via Sysl

Re: Patch Review Help needed

I will take a look at a few of these today. Thanks got your patches Ashish! On Sunday, December 8, 2013, Ashish wrote: > Folks, > > Need help in reviewing the following patches. > > FLUME-2243 - AvroSource to use TransceiverThreadFactory for Thread naming > while initializing NioServerSocketChann

[jira] [Commented] (FLUME-2243) AvroSource to use TransceiverThreadFactory for Thread naming while initializing NioServerSocketChannelFactory

[ https://issues.apache.org/jira/browse/FLUME-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843237#comment-13843237 ] Gopinathan A commented on FLUME-2243: - +1 for patch > AvroSource to use TransceiverTh

[jira] [Commented] (FLUME-2006) in Avro the batch size is called batch-size, in all other sources batchSize

[ https://issues.apache.org/jira/browse/FLUME-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843236#comment-13843236 ] Ashish Paliwal commented on FLUME-2006: --- Almost done with patch. Verifying the chang

[jira] [Updated] (FLUME-2259) transaction closure not happening for all the scenario in hbasesink

[ https://issues.apache.org/jira/browse/FLUME-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopinathan A updated FLUME-2259: Attachment: FLUME-2259.patch > transaction closure not happening for all the scenario in hbasesink

[jira] [Commented] (FLUME-2228) HDFS namenode failover cause flume error

[ https://issues.apache.org/jira/browse/FLUME-2228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843086#comment-13843086 ] Sergey commented on FLUME-2228: --- And what we should do with unrolled files? Any mapreduce j

[jira] [Resolved] (FLUME-2249) Interceptors are failing to modify/drop events with log4j appender and avro source.

[ https://issues.apache.org/jira/browse/FLUME-2249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] V Paul resolved FLUME-2249. --- Resolution: Not A Problem Release Note: NAP, as commented above > Interceptors are failing to modify/dr