[jira] [Created] (APEXMALHAR-2542) enricher.ApplicationTest access to hard coded /tmp location

2017-09-25 Thread Thomas Weise (JIRA)
Thomas Weise created APEXMALHAR-2542:


 Summary: enricher.ApplicationTest access to hard coded /tmp 
location
 Key: APEXMALHAR-2542
 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2542
 Project: Apache Apex Malhar
  Issue Type: Bug
Reporter: Thomas Weise


{code}
2017-09-25 18:34:37,900 [3/Enrich:POJOEnricher] WARN  util.LoggerUtil 
shouldFetchLogFileInformation - Log information is unavailable. To enable log 
information log4j/logging should be configured with single FileAppender that 
has immediateFlush set to true and log level set to ERROR or greater.
2017-09-25 18:34:37,916 [3/Enrich:POJOEnricher] ERROR engine.StreamingContainer 
run - Abandoning deployment of operator 
OperatorDeployInfo[id=3,name=Enrich,type=GENERIC,checkpoint={, 
0, 
0},inputs=[OperatorDeployInfo.InputDeployInfo[portName=input,streamId=Enrich,sourceNodeId=2,sourcePortName=out,locality=,partitionMask=0,partitionKeys=]],outputs=[OperatorDeployInfo.OutputDeployInfo[portName=output,streamId=Console,bufferServer=localhost]]]
 due to setup failure.
java.lang.RuntimeException: Unable to initialize cache manager
at 
com.datatorrent.contrib.enrich.AbstractEnricher.activate(AbstractEnricher.java:191)
at 
com.datatorrent.contrib.enrich.POJOEnricher.activate(POJOEnricher.java:234)
at com.datatorrent.stram.engine.Node.activate(Node.java:644)
at 
com.datatorrent.stram.engine.GenericNode.activate(GenericNode.java:212)
at 
com.datatorrent.stram.engine.StreamingContainer.setupNode(StreamingContainer.java:1364)
at 
com.datatorrent.stram.engine.StreamingContainer.access$100(StreamingContainer.java:129)
at 
com.datatorrent.stram.engine.StreamingContainer$2.run(StreamingContainer.java:1413)
Caused by: java.io.IOException: Provided path /tmp/circleMapping.txt is not a 
file
at com.datatorrent.contrib.enrich.FSLoader.connect(FSLoader.java:190)
at 
com.datatorrent.lib.db.cache.CacheManager.initialize(CacheManager.java:109)
at 
com.datatorrent.contrib.enrich.AbstractEnricher.activate(AbstractEnricher.java:189)
{code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (APEXMALHAR-2543) filter.ApplicationTest error but test passes

2017-09-25 Thread Thomas Weise (JIRA)
Thomas Weise created APEXMALHAR-2543:


 Summary: filter.ApplicationTest error but test passes
 Key: APEXMALHAR-2543
 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2543
 Project: Apache Apex Malhar
  Issue Type: Bug
Reporter: Thomas Weise
Priority: Minor


{code}
java.io.FileNotFoundException: File does not exist: 
target/org.apache.apex.examples.filter.ApplicationTest/testApplication
at org.apache.commons.io.FileUtils.forceDelete(FileUtils.java:2275)
at 
org.apache.apex.examples.filter.ApplicationTest$TestMeta.finished(ApplicationTest.java:64)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at org.junit.rules.RunRules.evaluate(RunRules.java:18)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:24)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
{code}




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (APEXMALHAR-2544) Flume test leads to Travis timeout

2017-09-25 Thread Thomas Weise (JIRA)
Thomas Weise created APEXMALHAR-2544:


 Summary: Flume test leads to Travis timeout
 Key: APEXMALHAR-2544
 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2544
 Project: Apache Apex Malhar
  Issue Type: Bug
Reporter: Thomas Weise


Seen in two subsequent instances.

https://travis-ci.org/apache/apex-malhar/pull_requests

{code}
---
 T E S T S
---
Picked up _JAVA_OPTIONS: -Xmx2048m -Xms512m
Running org.apache.apex.malhar.flume.sink.ServerTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.08 sec - in 
org.apache.apex.malhar.flume.sink.ServerTest
Running org.apache.apex.malhar.flume.sink.FlumeSinkTest


No output has been received in the last 10m0s, this potentially indicates a 
stalled build or something wrong with the build itself.
Check the details on how to adjust your build configuration on: 
https://docs.travis-ci.com/user/common-build-problems/#Build-times-out-because-no-output-was-received

The build has been terminated
{code}




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Assigned] (APEXMALHAR-2544) Flume test leads to Travis timeout

2017-09-25 Thread Ananth (JIRA)

 [ 
https://issues.apache.org/jira/browse/APEXMALHAR-2544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ananth reassigned APEXMALHAR-2544:
--

Assignee: Ananth

> Flume test leads to Travis timeout
> --
>
> Key: APEXMALHAR-2544
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2544
> Project: Apache Apex Malhar
>  Issue Type: Bug
>Reporter: Thomas Weise
>Assignee: Ananth
>
> Seen in two subsequent instances.
> https://travis-ci.org/apache/apex-malhar/pull_requests
> {code}
> ---
>  T E S T S
> ---
> Picked up _JAVA_OPTIONS: -Xmx2048m -Xms512m
> Running org.apache.apex.malhar.flume.sink.ServerTest
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.08 sec - in 
> org.apache.apex.malhar.flume.sink.ServerTest
> Running org.apache.apex.malhar.flume.sink.FlumeSinkTest
> No output has been received in the last 10m0s, this potentially indicates a 
> stalled build or something wrong with the build itself.
> Check the details on how to adjust your build configuration on: 
> https://docs.travis-ci.com/user/common-build-problems/#Build-times-out-because-no-output-was-received
> The build has been terminated
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Assigned] (APEXMALHAR-2544) Flume test leads to Travis timeout

2017-09-25 Thread Ananth (JIRA)

 [ 
https://issues.apache.org/jira/browse/APEXMALHAR-2544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ananth reassigned APEXMALHAR-2544:
--

Assignee: (was: Ananth)

> Flume test leads to Travis timeout
> --
>
> Key: APEXMALHAR-2544
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2544
> Project: Apache Apex Malhar
>  Issue Type: Bug
>Reporter: Thomas Weise
>
> Seen in two subsequent instances.
> https://travis-ci.org/apache/apex-malhar/pull_requests
> {code}
> ---
>  T E S T S
> ---
> Picked up _JAVA_OPTIONS: -Xmx2048m -Xms512m
> Running org.apache.apex.malhar.flume.sink.ServerTest
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.08 sec - in 
> org.apache.apex.malhar.flume.sink.ServerTest
> Running org.apache.apex.malhar.flume.sink.FlumeSinkTest
> No output has been received in the last 10m0s, this potentially indicates a 
> stalled build or something wrong with the build itself.
> Check the details on how to adjust your build configuration on: 
> https://docs.travis-ci.com/user/common-build-problems/#Build-times-out-because-no-output-was-received
> The build has been terminated
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Assigned] (APEXMALHAR-2542) enricher.ApplicationTest access to hard coded /tmp location

2017-09-25 Thread Ananth (JIRA)

 [ 
https://issues.apache.org/jira/browse/APEXMALHAR-2542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ananth reassigned APEXMALHAR-2542:
--

Assignee: Ananth

> enricher.ApplicationTest access to hard coded /tmp location
> ---
>
> Key: APEXMALHAR-2542
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2542
> Project: Apache Apex Malhar
>  Issue Type: Bug
>Reporter: Thomas Weise
>Assignee: Ananth
>
> {code}
> 2017-09-25 18:34:37,900 [3/Enrich:POJOEnricher] WARN  util.LoggerUtil 
> shouldFetchLogFileInformation - Log information is unavailable. To enable log 
> information log4j/logging should be configured with single FileAppender that 
> has immediateFlush set to true and log level set to ERROR or greater.
> 2017-09-25 18:34:37,916 [3/Enrich:POJOEnricher] ERROR 
> engine.StreamingContainer run - Abandoning deployment of operator 
> OperatorDeployInfo[id=3,name=Enrich,type=GENERIC,checkpoint={,
>  0, 
> 0},inputs=[OperatorDeployInfo.InputDeployInfo[portName=input,streamId=Enrich,sourceNodeId=2,sourcePortName=out,locality=,partitionMask=0,partitionKeys=]],outputs=[OperatorDeployInfo.OutputDeployInfo[portName=output,streamId=Console,bufferServer=localhost]]]
>  due to setup failure.
> java.lang.RuntimeException: Unable to initialize cache manager
>   at 
> com.datatorrent.contrib.enrich.AbstractEnricher.activate(AbstractEnricher.java:191)
>   at 
> com.datatorrent.contrib.enrich.POJOEnricher.activate(POJOEnricher.java:234)
>   at com.datatorrent.stram.engine.Node.activate(Node.java:644)
>   at 
> com.datatorrent.stram.engine.GenericNode.activate(GenericNode.java:212)
>   at 
> com.datatorrent.stram.engine.StreamingContainer.setupNode(StreamingContainer.java:1364)
>   at 
> com.datatorrent.stram.engine.StreamingContainer.access$100(StreamingContainer.java:129)
>   at 
> com.datatorrent.stram.engine.StreamingContainer$2.run(StreamingContainer.java:1413)
> Caused by: java.io.IOException: Provided path /tmp/circleMapping.txt is not a 
> file
>   at com.datatorrent.contrib.enrich.FSLoader.connect(FSLoader.java:190)
>   at 
> com.datatorrent.lib.db.cache.CacheManager.initialize(CacheManager.java:109)
>   at 
> com.datatorrent.contrib.enrich.AbstractEnricher.activate(AbstractEnricher.java:189)
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (APEXMALHAR-2545) Implement a few improvements in the Kudu Implementation

2017-09-25 Thread Ananth (JIRA)
Ananth created APEXMALHAR-2545:
--

 Summary: Implement a few improvements in the Kudu Implementation
 Key: APEXMALHAR-2545
 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2545
 Project: Apache Apex Malhar
  Issue Type: Bug
Reporter: Ananth
Assignee: Ananth


There are some minor improvements that need to be done as per the Kudu operator 
review. 

- Ensure logging is not ERROR level for some of the parser logic wrappers. For 
example, in the unit tests, we are seeing error logs and it is not necessary 
they are errors given we send all erraneous SQL expressions to an error port. 
i.e. the operator is continuing as if it were not an error
- Ensure that the operator properties are configurable per environment using 
the configuration object
- Optimise the setters logic for a given query.




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (APEXMALHAR-2545) Implement few improvements in the Kudu Implementation

2017-09-25 Thread Ananth (JIRA)

 [ 
https://issues.apache.org/jira/browse/APEXMALHAR-2545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ananth updated APEXMALHAR-2545:
---
Summary: Implement few improvements in the Kudu Implementation  (was: 
Implement a few improvements in the Kudu Implementation)

> Implement few improvements in the Kudu Implementation
> -
>
> Key: APEXMALHAR-2545
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2545
> Project: Apache Apex Malhar
>  Issue Type: Bug
>Reporter: Ananth
>Assignee: Ananth
>
> There are some minor improvements that need to be done as per the Kudu 
> operator review. 
> - Ensure logging is not ERROR level for some of the parser logic wrappers. 
> For example, in the unit tests, we are seeing error logs and it is not 
> necessary they are errors given we send all erraneous SQL expressions to an 
> error port. i.e. the operator is continuing as if it were not an error
> - Ensure that the operator properties are configurable per environment using 
> the configuration object
> - Optimise the setters logic for a given query.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (APEXMALHAR-2546) Mocking dependencies should ideally be in the maven parent instead of individual modules

2017-09-25 Thread Ananth (JIRA)
Ananth created APEXMALHAR-2546:
--

 Summary: Mocking dependencies should ideally be in the maven 
parent instead of individual modules 
 Key: APEXMALHAR-2546
 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2546
 Project: Apache Apex Malhar
  Issue Type: Improvement
Reporter: Ananth
Assignee: Ananth
Priority: Minor


There are a couple of Mocking dependencies that were introduced in the Kudu 
implementation but the right fit for those mocking libraries is the top level 
parent. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)