You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "wolfgang hoschek (JIRA)" <ji...@apache.org> on 2012/11/08 05:08:12 UTC
[jira] [Created] (FLUME-1690) Elastic Search Sink doesn't run it's
unit tests
wolfgang hoschek created FLUME-1690:
---------------------------------------
Summary: Elastic Search Sink doesn't run it's unit tests
Key: FLUME-1690
URL: https://issues.apache.org/jira/browse/FLUME-1690
Project: Flume
Issue Type: Bug
Components: Sinks+Sources
Affects Versions: v1.3.0
Reporter: wolfgang hoschek
I noticed that Elastic Search Sink doesn't run it's unit tests because they end with *Test rather than start with Test*. It's because top level pom defines this:
<test.include.pattern>**/Test*.java</test.include.pattern>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FLUME-1690) Elastic Search Sink doesn't run
it's unit tests
Posted by "wolfgang hoschek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13493562#comment-13493562 ]
wolfgang hoschek commented on FLUME-1690:
-----------------------------------------
I'm pretty swamped right now. I think fix is to either add to the test.include.pattern or change the name of test java files.
> Elastic Search Sink doesn't run it's unit tests
> -----------------------------------------------
>
> Key: FLUME-1690
> URL: https://issues.apache.org/jira/browse/FLUME-1690
> Project: Flume
> Issue Type: Bug
> Components: Sinks+Sources
> Affects Versions: v1.3.0
> Reporter: wolfgang hoschek
> Assignee: Hari Shreedharan
> Attachments: FLUME-1690.patch
>
>
> I noticed that Elastic Search Sink doesn't run it's unit tests because they end with *Test rather than start with Test*. It's because top level pom defines this:
> <test.include.pattern>**/Test*.java</test.include.pattern>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FLUME-1690) Elastic Search Sink doesn't run
it's unit tests
Posted by "Hari Shreedharan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13493567#comment-13493567 ]
Hari Shreedharan commented on FLUME-1690:
-----------------------------------------
I changed the names of the files.
> Elastic Search Sink doesn't run it's unit tests
> -----------------------------------------------
>
> Key: FLUME-1690
> URL: https://issues.apache.org/jira/browse/FLUME-1690
> Project: Flume
> Issue Type: Bug
> Components: Sinks+Sources
> Affects Versions: v1.3.0
> Reporter: wolfgang hoschek
> Assignee: Hari Shreedharan
> Attachments: FLUME-1690.patch
>
>
> I noticed that Elastic Search Sink doesn't run it's unit tests because they end with *Test rather than start with Test*. It's because top level pom defines this:
> <test.include.pattern>**/Test*.java</test.include.pattern>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FLUME-1690) Elastic Search Sink doesn't run
it's unit tests
Posted by "Hari Shreedharan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13493503#comment-13493503 ]
Hari Shreedharan commented on FLUME-1690:
-----------------------------------------
Yep. You are right. Are you looking into this? If not, I can submit a patch.
> Elastic Search Sink doesn't run it's unit tests
> -----------------------------------------------
>
> Key: FLUME-1690
> URL: https://issues.apache.org/jira/browse/FLUME-1690
> Project: Flume
> Issue Type: Bug
> Components: Sinks+Sources
> Affects Versions: v1.3.0
> Reporter: wolfgang hoschek
>
> I noticed that Elastic Search Sink doesn't run it's unit tests because they end with *Test rather than start with Test*. It's because top level pom defines this:
> <test.include.pattern>**/Test*.java</test.include.pattern>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FLUME-1690) Elastic Search Sink doesn't run it's
unit tests
Posted by "Hari Shreedharan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hari Shreedharan updated FLUME-1690:
------------------------------------
Fix Version/s: v1.3.0
> Elastic Search Sink doesn't run it's unit tests
> -----------------------------------------------
>
> Key: FLUME-1690
> URL: https://issues.apache.org/jira/browse/FLUME-1690
> Project: Flume
> Issue Type: Bug
> Components: Sinks+Sources
> Affects Versions: v1.3.0
> Reporter: wolfgang hoschek
> Assignee: Hari Shreedharan
> Fix For: v1.3.0
>
> Attachments: FLUME-1690.patch
>
>
> I noticed that Elastic Search Sink doesn't run it's unit tests because they end with *Test rather than start with Test*. It's because top level pom defines this:
> <test.include.pattern>**/Test*.java</test.include.pattern>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FLUME-1690) Elastic Search Sink doesn't run
it's unit tests
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13494511#comment-13494511 ]
Hudson commented on FLUME-1690:
-------------------------------
Integrated in flume-trunk #323 (See [https://builds.apache.org/job/flume-trunk/323/])
FLUME-1690: Elastic Search Sink doesn't run it's unit tests (Revision 107875af508541ab73311c875b6043b2eeab2da3)
Result = SUCCESS
brock : http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git&a=commit&h=107875af508541ab73311c875b6043b2eeab2da3
Files :
* flume-ng-sinks/flume-ng-elasticsearch-sink/src/test/java/org/apache/flume/sink/elasticsearch/TestElasticSearchDynamicSerializer.java
* flume-ng-sinks/flume-ng-elasticsearch-sink/src/test/java/org/apache/flume/sink/elasticsearch/ElasticSearchDynamicSerializerTest.java
* flume-ng-sinks/flume-ng-elasticsearch-sink/src/test/java/org/apache/flume/sink/elasticsearch/TestElasticSearchLogStashEventSerializer.java
* flume-ng-sinks/flume-ng-elasticsearch-sink/src/test/java/org/apache/flume/sink/elasticsearch/TestElasticSearchSink.java
* flume-ng-sinks/flume-ng-elasticsearch-sink/src/test/java/org/apache/flume/sink/elasticsearch/ElasticSearchSinkTest.java
* flume-ng-sinks/flume-ng-elasticsearch-sink/src/test/java/org/apache/flume/sink/elasticsearch/ElasticSearchLogStashEventSerializerTest.java
> Elastic Search Sink doesn't run it's unit tests
> -----------------------------------------------
>
> Key: FLUME-1690
> URL: https://issues.apache.org/jira/browse/FLUME-1690
> Project: Flume
> Issue Type: Bug
> Components: Sinks+Sources
> Affects Versions: v1.3.0
> Reporter: wolfgang hoschek
> Assignee: Hari Shreedharan
> Fix For: v1.3.0
>
> Attachments: FLUME-1690.patch
>
>
> I noticed that Elastic Search Sink doesn't run it's unit tests because they end with *Test rather than start with Test*. It's because top level pom defines this:
> <test.include.pattern>**/Test*.java</test.include.pattern>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FLUME-1690) Elastic Search Sink doesn't run it's
unit tests
Posted by "Hari Shreedharan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hari Shreedharan updated FLUME-1690:
------------------------------------
Attachment: FLUME-1690.patch
> Elastic Search Sink doesn't run it's unit tests
> -----------------------------------------------
>
> Key: FLUME-1690
> URL: https://issues.apache.org/jira/browse/FLUME-1690
> Project: Flume
> Issue Type: Bug
> Components: Sinks+Sources
> Affects Versions: v1.3.0
> Reporter: wolfgang hoschek
> Attachments: FLUME-1690.patch
>
>
> I noticed that Elastic Search Sink doesn't run it's unit tests because they end with *Test rather than start with Test*. It's because top level pom defines this:
> <test.include.pattern>**/Test*.java</test.include.pattern>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (FLUME-1690) Elastic Search Sink doesn't run it's
unit tests
Posted by "Hari Shreedharan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hari Shreedharan reassigned FLUME-1690:
---------------------------------------
Assignee: Hari Shreedharan
> Elastic Search Sink doesn't run it's unit tests
> -----------------------------------------------
>
> Key: FLUME-1690
> URL: https://issues.apache.org/jira/browse/FLUME-1690
> Project: Flume
> Issue Type: Bug
> Components: Sinks+Sources
> Affects Versions: v1.3.0
> Reporter: wolfgang hoschek
> Assignee: Hari Shreedharan
> Attachments: FLUME-1690.patch
>
>
> I noticed that Elastic Search Sink doesn't run it's unit tests because they end with *Test rather than start with Test*. It's because top level pom defines this:
> <test.include.pattern>**/Test*.java</test.include.pattern>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira