[jira] [Commented] (FLUME-2310) after reloading configuration at runtime, JMX monitoring metrics doesn't updates without restarting flume.
[ https://issues.apache.org/jira/browse/FLUME-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890484#comment-13890484 ] minseok kim commented on FLUME-2310: i found that this issue has already fixed in trunk sourcecode. (https://git-wip-us.apache.org/repos/asf/flume.git flume-ng-core/src/main/java/org/apache/flume/instrumentation/MonitoredCounterGroup.java) may i ask when this fix will be released? after reloading configuration at runtime, JMX monitoring metrics doesn't updates without restarting flume. --- Key: FLUME-2310 URL: https://issues.apache.org/jira/browse/FLUME-2310 Project: Flume Issue Type: Bug Components: Configuration Affects Versions: v1.4.0 Environment: centos 6.3 Reporter: minseok kim Priority: Minor flume provides JMX monitoring interface by following extra arguments. -Dflume.monitoring.type=http -Dflume.monitoring.port= and user can monitor flume via web browser. after flume reloading its configuration at runtime, related jmx metrics doesn't automatically with following error log. log says that error occurs when re-registering MBean to JMXServer because of the already registered MBean. regardless of this error, other feature such as gathering log still works. - 2014/02/04 15:33:17,997/KST ERROR lifecycleSupervisor-1-2 - Failed to register monitored counter group for type: CHANNEL, name: channel1 (instrumentation.MonitoredCounterGroup.register:113) javax.management.InstanceAlreadyExistsException: org.apache.flume.channel:type=channel1 at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312) at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482) at org.apache.flume.instrumentation.MonitoredCounterGroup.register(MonitoredCounterGroup.java:108) at org.apache.flume.instrumentation.MonitoredCounterGroup.start(MonitoredCounterGroup.java:88) at org.apache.flume.channel.file.FileChannel.start(FileChannel.java:319) at org.apache.flume.lifecycle.LifecycleSupervisor$MonitorRunnable.run(LifecycleSupervisor.java:251) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) 2014/02/04 15:33:17,999/KST INFO lifecycleSupervisor-1-2 - Component type: CHANNEL, name: channel1 started -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (FLUME-2310) after reloading configuration at runtime, JMX monitoring metrics doesn't updates without restarting flume.
[ https://issues.apache.org/jira/browse/FLUME-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890487#comment-13890487 ] Ashish Paliwal commented on FLUME-2310: --- Next release shall happen in coming few weeks. We recently had a related discussion on Dev ML after reloading configuration at runtime, JMX monitoring metrics doesn't updates without restarting flume. --- Key: FLUME-2310 URL: https://issues.apache.org/jira/browse/FLUME-2310 Project: Flume Issue Type: Bug Components: Configuration Affects Versions: v1.4.0 Environment: centos 6.3 Reporter: minseok kim Priority: Minor flume provides JMX monitoring interface by following extra arguments. -Dflume.monitoring.type=http -Dflume.monitoring.port= and user can monitor flume via web browser. after flume reloading its configuration at runtime, related jmx metrics doesn't automatically with following error log. log says that error occurs when re-registering MBean to JMXServer because of the already registered MBean. regardless of this error, other feature such as gathering log still works. - 2014/02/04 15:33:17,997/KST ERROR lifecycleSupervisor-1-2 - Failed to register monitored counter group for type: CHANNEL, name: channel1 (instrumentation.MonitoredCounterGroup.register:113) javax.management.InstanceAlreadyExistsException: org.apache.flume.channel:type=channel1 at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312) at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482) at org.apache.flume.instrumentation.MonitoredCounterGroup.register(MonitoredCounterGroup.java:108) at org.apache.flume.instrumentation.MonitoredCounterGroup.start(MonitoredCounterGroup.java:88) at org.apache.flume.channel.file.FileChannel.start(FileChannel.java:319) at org.apache.flume.lifecycle.LifecycleSupervisor$MonitorRunnable.run(LifecycleSupervisor.java:251) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) 2014/02/04 15:33:17,999/KST INFO lifecycleSupervisor-1-2 - Component type: CHANNEL, name: channel1 started -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (FLUME-2310) after reloading configuration at runtime, JMX monitoring metrics doesn't updates without restarting flume.
[ https://issues.apache.org/jira/browse/FLUME-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890488#comment-13890488 ] minseok kim commented on FLUME-2310: oh that's great. thank you for quick replay. after reloading configuration at runtime, JMX monitoring metrics doesn't updates without restarting flume. --- Key: FLUME-2310 URL: https://issues.apache.org/jira/browse/FLUME-2310 Project: Flume Issue Type: Bug Components: Configuration Affects Versions: v1.4.0 Environment: centos 6.3 Reporter: minseok kim Priority: Minor flume provides JMX monitoring interface by following extra arguments. -Dflume.monitoring.type=http -Dflume.monitoring.port= and user can monitor flume via web browser. after flume reloading its configuration at runtime, related jmx metrics doesn't automatically with following error log. log says that error occurs when re-registering MBean to JMXServer because of the already registered MBean. regardless of this error, other feature such as gathering log still works. - 2014/02/04 15:33:17,997/KST ERROR lifecycleSupervisor-1-2 - Failed to register monitored counter group for type: CHANNEL, name: channel1 (instrumentation.MonitoredCounterGroup.register:113) javax.management.InstanceAlreadyExistsException: org.apache.flume.channel:type=channel1 at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312) at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482) at org.apache.flume.instrumentation.MonitoredCounterGroup.register(MonitoredCounterGroup.java:108) at org.apache.flume.instrumentation.MonitoredCounterGroup.start(MonitoredCounterGroup.java:88) at org.apache.flume.channel.file.FileChannel.start(FileChannel.java:319) at org.apache.flume.lifecycle.LifecycleSupervisor$MonitorRunnable.run(LifecycleSupervisor.java:251) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) 2014/02/04 15:33:17,999/KST INFO lifecycleSupervisor-1-2 - Component type: CHANNEL, name: channel1 started -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (FLUME-924) Implement a JMS source for Flume NG
[ https://issues.apache.org/jira/browse/FLUME-924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890651#comment-13890651 ] Hugo Lassiège commented on FLUME-924: - Hi, I'm currently using this jms source to connect on Weblogic message bus. I'm wondering why the JMSMessageConsumer use createQueue and createTopic instead of lookup to find the destinations (line 83 to 90). It seems that createQueue or createTopic are not the recommended way because it is not portable (I saw that warning in Weblogic documentation even if I can't justify this assertion). The documentation recommends to use a JNDI lookup (http://docs.oracle.com/cd/E23943_01/web./e13727/lookup.htm#BABDFCIC). Is there any reason to use createQueue instead of lookup ? I'm asking that because the configuration of Flume with a clusterised Weblogic server is not straightforward and I still can't get to make it work. Regards, Hugo Implement a JMS source for Flume NG --- Key: FLUME-924 URL: https://issues.apache.org/jira/browse/FLUME-924 Project: Flume Issue Type: New Feature Affects Versions: v1.0.0 Reporter: Bruno Mahé Assignee: Brock Noland Fix For: v1.4.0 Attachments: FLUME-924-1.patch, FLUME-924-2.patch, FLUME-924-3.patch, FLUME-924-5.patch, FLUME-924-6.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (FLUME-2311) Use standard way of finding queue/topic
Brock Noland created FLUME-2311: --- Summary: Use standard way of finding queue/topic Key: FLUME-2311 URL: https://issues.apache.org/jira/browse/FLUME-2311 Project: Flume Issue Type: Bug Reporter: Brock Noland Here https://issues.apache.org/jira/browse/FLUME-924?focusedCommentId=13890651page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13890651 [~hlassiege] says: I'm currently using this jms source to connect on Weblogic message bus. I'm wondering why the JMSMessageConsumer use createQueue and createTopic instead of lookup to find the destinations (line 83 to 90). It seems that createQueue or createTopic are not the recommended way because it is not portable (I saw that warning in Weblogic documentation even if I can't justify this assertion). The documentation recommends to use a JNDI lookup (http://docs.oracle.com/cd/E23943_01/web./e13727/lookup.htm#BABDFCIC). Is there any reason to use createQueue instead of lookup ? -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (FLUME-924) Implement a JMS source for Flume NG
[ https://issues.apache.org/jira/browse/FLUME-924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890899#comment-13890899 ] Brock Noland commented on FLUME-924: Hi, There is no particular reason...I created FLUME-2311 for your suggestion. I will comment there. Implement a JMS source for Flume NG --- Key: FLUME-924 URL: https://issues.apache.org/jira/browse/FLUME-924 Project: Flume Issue Type: New Feature Affects Versions: v1.0.0 Reporter: Bruno Mahé Assignee: Brock Noland Fix For: v1.4.0 Attachments: FLUME-924-1.patch, FLUME-924-2.patch, FLUME-924-3.patch, FLUME-924-5.patch, FLUME-924-6.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (FLUME-2311) Use standard way of finding queue/topic
[ https://issues.apache.org/jira/browse/FLUME-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890901#comment-13890901 ] Brock Noland commented on FLUME-2311: - [~hlassiege], would you be in a position to make the change and see if it fixes your issues? Use standard way of finding queue/topic --- Key: FLUME-2311 URL: https://issues.apache.org/jira/browse/FLUME-2311 Project: Flume Issue Type: Bug Reporter: Brock Noland Here https://issues.apache.org/jira/browse/FLUME-924?focusedCommentId=13890651page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13890651 [~hlassiege] says: I'm currently using this jms source to connect on Weblogic message bus. I'm wondering why the JMSMessageConsumer use createQueue and createTopic instead of lookup to find the destinations (line 83 to 90). It seems that createQueue or createTopic are not the recommended way because it is not portable (I saw that warning in Weblogic documentation even if I can't justify this assertion). The documentation recommends to use a JNDI lookup (http://docs.oracle.com/cd/E23943_01/web./e13727/lookup.htm#BABDFCIC). Is there any reason to use createQueue instead of lookup ? -- This message was sent by Atlassian JIRA (v6.1.5#6160)
Re: Review Request 16650: FLUME-2225 Elasticsearch Sink for ES HTTP API
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/16650/ --- (Updated Feb. 4, 2014, 6:45 p.m.) Review request for Flume, Brock Noland, Hari Shreedharan, and Mike Percy. Repository: flume-git Description --- The patch contains changes in elasticsearch sink. It gives possibility to swich between Transport Client and REST Client to elasticsearch. Jest library (https://github.com/searchbox-io/Jest) client was used to communicate with elasticsearch by HTTP API. It uses guava 14 so it was necessary also to change version of guava used in flume (11.0.2 - 14.0.1) Patch FLUME-2225-0.patch Diffs (updated) - flume-ng-core/pom.xml e41bcc2 flume-ng-core/src/main/java/org/apache/flume/source/SyslogParser.java 557d121 flume-ng-sinks/flume-ng-elasticsearch-sink/pom.xml bdc21d1 flume-ng-sinks/flume-ng-elasticsearch-sink/src/main/java/org/apache/flume/sink/elasticsearch/AbstractElasticSearchIndexRequestBuilderFactory.java 6effe34 flume-ng-sinks/flume-ng-elasticsearch-sink/src/main/java/org/apache/flume/sink/elasticsearch/ElasticSearchIndexRequestBuilderFactory.java 8e77a1e flume-ng-sinks/flume-ng-elasticsearch-sink/src/main/java/org/apache/flume/sink/elasticsearch/ElasticSearchSink.java e38ab19 flume-ng-sinks/flume-ng-elasticsearch-sink/src/main/java/org/apache/flume/sink/elasticsearch/ElasticSearchSinkConstants.java dd0c59d flume-ng-sinks/flume-ng-elasticsearch-sink/src/main/java/org/apache/flume/sink/elasticsearch/EventSerializerIndexRequestBuilderFactory.java c71b2e5 flume-ng-sinks/flume-ng-elasticsearch-sink/src/main/java/org/apache/flume/sink/elasticsearch/IndexNameBuilder.java PRE-CREATION flume-ng-sinks/flume-ng-elasticsearch-sink/src/main/java/org/apache/flume/sink/elasticsearch/TimeBasedIndexNameBuilder.java PRE-CREATION flume-ng-sinks/flume-ng-elasticsearch-sink/src/main/java/org/apache/flume/sink/elasticsearch/TimestampedEvent.java PRE-CREATION flume-ng-sinks/flume-ng-elasticsearch-sink/src/main/java/org/apache/flume/sink/elasticsearch/client/ElasticSearchClient.java PRE-CREATION flume-ng-sinks/flume-ng-elasticsearch-sink/src/main/java/org/apache/flume/sink/elasticsearch/client/ElasticSearchClientFactory.java PRE-CREATION flume-ng-sinks/flume-ng-elasticsearch-sink/src/main/java/org/apache/flume/sink/elasticsearch/client/ElasticSearchRestClient.java PRE-CREATION flume-ng-sinks/flume-ng-elasticsearch-sink/src/main/java/org/apache/flume/sink/elasticsearch/client/ElasticSearchTransportClient.java PRE-CREATION flume-ng-sinks/flume-ng-elasticsearch-sink/src/test/java/org/apache/flume/sink/elasticsearch/TestElasticSearchDynamicSerializer.java 43a4b12 flume-ng-sinks/flume-ng-elasticsearch-sink/src/test/java/org/apache/flume/sink/elasticsearch/TestElasticSearchIndexRequestBuilderFactory.java 1e4e119 flume-ng-sinks/flume-ng-elasticsearch-sink/src/test/java/org/apache/flume/sink/elasticsearch/TestElasticSearchLogStashEventSerializer.java 9dff4b0 flume-ng-sinks/flume-ng-elasticsearch-sink/src/test/java/org/apache/flume/sink/elasticsearch/TestElasticSearchSink.java 71789e8 flume-ng-sinks/flume-ng-elasticsearch-sink/src/test/java/org/apache/flume/sink/elasticsearch/TimeBasedIndexNameBuilderTest.java PRE-CREATION flume-ng-sinks/flume-ng-elasticsearch-sink/src/test/java/org/apache/flume/sink/elasticsearch/TimestampedEventTest.java PRE-CREATION flume-ng-sinks/flume-ng-elasticsearch-sink/src/test/java/org/apache/flume/sink/elasticsearch/client/TestElasticSearchClientFactory.java PRE-CREATION flume-ng-sinks/flume-ng-elasticsearch-sink/src/test/java/org/apache/flume/sink/elasticsearch/client/TestElasticSearchRestClient.java PRE-CREATION flume-ng-sinks/flume-ng-elasticsearch-sink/src/test/java/org/apache/flume/sink/elasticsearch/client/TestElasticSearchTransportClient.java PRE-CREATION pom.xml 3c741c3 Diff: https://reviews.apache.org/r/16650/diff/ Testing --- Thanks, Pawe?
[jira] [Commented] (FLUME-2225) Elasticsearch Sink for ES HTTP API
[ https://issues.apache.org/jira/browse/FLUME-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890996#comment-13890996 ] Pawel commented on FLUME-2225: -- Hi, I attached a new patchset. I'll analyze it and try to find something to change, but I'll be also glad if you can watch that patchset. Elasticsearch Sink for ES HTTP API -- Key: FLUME-2225 URL: https://issues.apache.org/jira/browse/FLUME-2225 Project: Flume Issue Type: New Feature Affects Versions: v1.5.0 Reporter: Otis Gospodnetic Fix For: v1.4.1, v1.5.0 Attachments: FLUME-2225-0.patch, FLUME-2225-1.patch Existing ElasticSearchSink uses ES TransportClient. As such, one cannot use the ES HTTP API, which is sometimes easier, and doesn't have issues around client and server/cluster components using incompatible versions - currently, both client and server/cluster need to be on the same version. See http://search-hadoop.com/m/k76HH9Te68/otissubj=Elasticsearch+sink+that+uses+HTTP+API -- This message was sent by Atlassian JIRA (v6.1.5#6160)
Re: Review Request 16650: FLUME-2225 Elasticsearch Sink for ES HTTP API
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/16650/ --- (Updated Feb. 5, 2014, 1:21 a.m.) Review request for Flume, Brock Noland, Hari Shreedharan, and Mike Percy. Repository: flume-git Description --- The patch contains changes in elasticsearch sink. It gives possibility to swich between Transport Client and REST Client to elasticsearch. Jest library (https://github.com/searchbox-io/Jest) client was used to communicate with elasticsearch by HTTP API. It uses guava 14 so it was necessary also to change version of guava used in flume (11.0.2 - 14.0.1) Patch FLUME-2225-0.patch Diffs (updated) - flume-ng-core/pom.xml e41bcc2 flume-ng-core/src/main/java/org/apache/flume/source/SyslogParser.java 557d121 flume-ng-sinks/flume-ng-elasticsearch-sink/pom.xml bdc21d1 flume-ng-sinks/flume-ng-elasticsearch-sink/src/main/java/org/apache/flume/sink/elasticsearch/AbstractElasticSearchIndexRequestBuilderFactory.java 6effe34 flume-ng-sinks/flume-ng-elasticsearch-sink/src/main/java/org/apache/flume/sink/elasticsearch/ElasticSearchIndexRequestBuilderFactory.java 8e77a1e flume-ng-sinks/flume-ng-elasticsearch-sink/src/main/java/org/apache/flume/sink/elasticsearch/ElasticSearchSink.java e38ab19 flume-ng-sinks/flume-ng-elasticsearch-sink/src/main/java/org/apache/flume/sink/elasticsearch/ElasticSearchSinkConstants.java dd0c59d flume-ng-sinks/flume-ng-elasticsearch-sink/src/main/java/org/apache/flume/sink/elasticsearch/EventSerializerIndexRequestBuilderFactory.java c71b2e5 flume-ng-sinks/flume-ng-elasticsearch-sink/src/main/java/org/apache/flume/sink/elasticsearch/IndexNameBuilder.java PRE-CREATION flume-ng-sinks/flume-ng-elasticsearch-sink/src/main/java/org/apache/flume/sink/elasticsearch/TimeBasedIndexNameBuilder.java PRE-CREATION flume-ng-sinks/flume-ng-elasticsearch-sink/src/main/java/org/apache/flume/sink/elasticsearch/TimestampedEvent.java PRE-CREATION flume-ng-sinks/flume-ng-elasticsearch-sink/src/main/java/org/apache/flume/sink/elasticsearch/client/ElasticSearchClient.java PRE-CREATION flume-ng-sinks/flume-ng-elasticsearch-sink/src/main/java/org/apache/flume/sink/elasticsearch/client/ElasticSearchClientFactory.java PRE-CREATION flume-ng-sinks/flume-ng-elasticsearch-sink/src/main/java/org/apache/flume/sink/elasticsearch/client/ElasticSearchRestClient.java PRE-CREATION flume-ng-sinks/flume-ng-elasticsearch-sink/src/main/java/org/apache/flume/sink/elasticsearch/client/ElasticSearchTransportClient.java PRE-CREATION flume-ng-sinks/flume-ng-elasticsearch-sink/src/main/java/org/apache/flume/sink/elasticsearch/client/NoSuchClientTypeException.java PRE-CREATION flume-ng-sinks/flume-ng-elasticsearch-sink/src/test/java/org/apache/flume/sink/elasticsearch/TestElasticSearchDynamicSerializer.java 43a4b12 flume-ng-sinks/flume-ng-elasticsearch-sink/src/test/java/org/apache/flume/sink/elasticsearch/TestElasticSearchIndexRequestBuilderFactory.java 1e4e119 flume-ng-sinks/flume-ng-elasticsearch-sink/src/test/java/org/apache/flume/sink/elasticsearch/TestElasticSearchLogStashEventSerializer.java 9dff4b0 flume-ng-sinks/flume-ng-elasticsearch-sink/src/test/java/org/apache/flume/sink/elasticsearch/TestElasticSearchSink.java 71789e8 flume-ng-sinks/flume-ng-elasticsearch-sink/src/test/java/org/apache/flume/sink/elasticsearch/TimeBasedIndexNameBuilderTest.java PRE-CREATION flume-ng-sinks/flume-ng-elasticsearch-sink/src/test/java/org/apache/flume/sink/elasticsearch/TimestampedEventTest.java PRE-CREATION flume-ng-sinks/flume-ng-elasticsearch-sink/src/test/java/org/apache/flume/sink/elasticsearch/client/TestElasticSearchClientFactory.java PRE-CREATION flume-ng-sinks/flume-ng-elasticsearch-sink/src/test/java/org/apache/flume/sink/elasticsearch/client/TestElasticSearchRestClient.java PRE-CREATION flume-ng-sinks/flume-ng-elasticsearch-sink/src/test/java/org/apache/flume/sink/elasticsearch/client/TestElasticSearchTransportClient.java PRE-CREATION pom.xml 3c741c3 Diff: https://reviews.apache.org/r/16650/diff/ Testing --- Thanks, Pawe?
[jira] [Assigned] (FLUME-2257) modify to ipFilterRules from ipFilter.rules in FlumeUserGuide
[ https://issues.apache.org/jira/browse/FLUME-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopinathan A reassigned FLUME-2257: --- Assignee: Gopinathan A modify to ipFilterRules from ipFilter.rules in FlumeUserGuide -- Key: FLUME-2257 URL: https://issues.apache.org/jira/browse/FLUME-2257 Project: Flume Issue Type: Bug Components: Docs Reporter: Gopinathan A Assignee: Gopinathan A Priority: Trivial Attachments: FLUME-2257.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
