Maven build package error with 3.5
It was running well with 3.4, but now failing with Apex 3.5
➜ log-aggregator git:(apex-tcp) ✗ mvn package -DskipTests
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building Aggregator 1.0-SNAPSHOT
[INFO]
Downloading:
https://repo.maven.apache.org/maven2/org/apache/apex/malhar-library/3.5.0/malhar-library-3.5.0.pom
Downloading:
https://repo.maven.apache.org/maven2/org/apache/apex/apex-api/3.5.0/apex-api-3.5.0.pom
Downloading:
https://repo.maven.apache.org/maven2/org/apache/apex/apex-common/3.5.0/apex-common-3.5.0.pom
Downloading:
https://repo.maven.apache.org/maven2/org/apache/apex/apex-engine/3.5.0/apex-engine-3.5.0.pom
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 10.435 s
[INFO] Finished at: 2017-02-27T15:03:06-08:00
[INFO] Final Memory: 11M/245M
[INFO]
[ERROR] Failed to execute goal on project log-aggregator: Could not resolve
dependencies for project
com.capitalone.vault8:log-aggregator:jar:1.0-SNAPSHOT: Failed to collect
dependencies at org.apache.apex:malhar-library:jar:3.5.0: Failed to read
artifact descriptor for org.apache.apex:malhar-library:jar:3.5.0: Could not
transfer artifact org.apache.apex:malhar-library:pom:3.5.0 from/to central (
https://repo.maven.apache.org/maven2):
sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
➜ log-aggregator git:(apex-tcp) ✗
The pom file is:
http://maven.apache.org/POM/4.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
4.0.0
com.mycom.teamx
log-aggregator
jar
1.0-SNAPSHOT
Aggregator
Log Aggregator
3.5.0
lib/*.jar
org.apache.maven.plugins
maven-eclipse-plugin
2.9
true
maven-compiler-plugin
3.3
UTF-8
1.7
1.7
true
false
true
true
maven-dependency-plugin
2.8
copy-dependencies
prepare-package
copy-dependencies
target/deps
runtime
maven-assembly-plugin
app-package-assembly
package
single
${project.artifactId}-${project.version}-apexapp
false
src/assemble/appPackage.xml
0755
${apex.apppackage.classpath}
${apex.version}
${project.groupId}
${project.artifactId}
${project.version}
${project.name}
${project.description}
maven-antrun-plugin
1.7
package
run
org.apache.apex
malhar-library
${apex.version}
*
*
org.apache.apex
apex-api
${apex.version}
org.apache.apex
apex-common
${apex.version}
*
*
junit
junit
4.10
test
org.apache.apex
apex-engine
${apex.version}
test
*
*
joda-time
joda-time
2.9.1
javax.validation
validation-api
1.1.0.Final
org.apache.hadoop
hadoop-common
2.3.0
Thanks,
- Dongming
[jira] [Closed] (APEXMALHAR-2420) Error in document for PI example
[ https://issues.apache.org/jira/browse/APEXMALHAR-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dongming Liang closed APEXMALHAR-2420. -- Resolution: Duplicate > Error in document for PI example > - > > Key: APEXMALHAR-2420 > URL: https://issues.apache.org/jira/browse/APEXMALHAR-2420 > Project: Apache Apex Malhar > Issue Type: Bug > Components: documentation >Affects Versions: 3.6.0 > Reporter: Dongming Liang > Assignee: Dongming Liang >Priority: Minor > > In Application_development document: > "PI is computed as N/number of values received" > should be: > "PI is computed as 4*N/number of values received" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (APEXMALHAR-2420) Error in document for PI example
[ https://issues.apache.org/jira/browse/APEXMALHAR-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15879556#comment-15879556 ] Dongming Liang commented on APEXMALHAR-2420: Moved to https://issues.apache.org/jira/browse/APEXCORE-651 > Error in document for PI example > - > > Key: APEXMALHAR-2420 > URL: https://issues.apache.org/jira/browse/APEXMALHAR-2420 > Project: Apache Apex Malhar > Issue Type: Bug > Components: documentation >Affects Versions: 3.6.0 > Reporter: Dongming Liang > Assignee: Dongming Liang >Priority: Minor > > In Application_development document: > "PI is computed as N/number of values received" > should be: > "PI is computed as 4*N/number of values received" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (APEXCORE-651) Error in document for PI example
Dongming Liang created APEXCORE-651: --- Summary: Error in document for PI example Key: APEXCORE-651 URL: https://issues.apache.org/jira/browse/APEXCORE-651 Project: Apache Apex Core Issue Type: Documentation Components: Documentation Reporter: Dongming Liang Priority: Minor In Application_development document: "PI is computed as N/number of values received" should be: "PI is computed as 4*N/number of values received" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (APEXMALHAR-2421) Error in document for PI example
[ https://issues.apache.org/jira/browse/APEXMALHAR-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dongming Liang closed APEXMALHAR-2421. -- Resolution: Duplicate > Error in document for PI example > - > > Key: APEXMALHAR-2421 > URL: https://issues.apache.org/jira/browse/APEXMALHAR-2421 > Project: Apache Apex Malhar > Issue Type: Bug > Components: documentation > Reporter: Dongming Liang > Assignee: Dongming Liang >Priority: Minor > > In Application_development document: > "PI is computed as N/number of values received" > should be: > "PI is computed as 4*N/number of values received" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (APEXMALHAR-2421) Error in document for PI example
Dongming Liang created APEXMALHAR-2421: -- Summary: Error in document for PI example Key: APEXMALHAR-2421 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2421 Project: Apache Apex Malhar Issue Type: Bug Components: documentation Reporter: Dongming Liang Assignee: Dongming Liang Priority: Minor In Application_development document: "PI is computed as N/number of values received" should be: "PI is computed as 4*N/number of values received" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (APEXMALHAR-2420) Error in document for PI example
[ https://issues.apache.org/jira/browse/APEXMALHAR-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15879541#comment-15879541 ] Dongming Liang commented on APEXMALHAR-2420: This should be filed under apex-core. Will move it. > Error in document for PI example > - > > Key: APEXMALHAR-2420 > URL: https://issues.apache.org/jira/browse/APEXMALHAR-2420 > Project: Apache Apex Malhar > Issue Type: Bug > Components: documentation >Affects Versions: 3.6.0 > Reporter: Dongming Liang > Assignee: Dongming Liang >Priority: Minor > > In Application_development document: > "PI is computed as N/number of values received" > should be: > "PI is computed as 4*N/number of values received" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (APEXMALHAR-2420) Error in document for PI example
Dongming Liang created APEXMALHAR-2420: -- Summary: Error in document for PI example Key: APEXMALHAR-2420 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2420 Project: Apache Apex Malhar Issue Type: Bug Components: documentation Affects Versions: 3.6.0 Reporter: Dongming Liang Assignee: Dongming Liang Priority: Minor In Application_development document: "PI is computed as N/number of values received" should be: "PI is computed as 4*N/number of values received" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (APEXMALHAR-2373) JdbcOutputOperator does not handle NUMERIC type
[
https://issues.apache.org/jira/browse/APEXMALHAR-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dongming Liang reassigned APEXMALHAR-2373:
--
Assignee: Dongming Liang
> JdbcOutputOperator does not handle NUMERIC type
> ---
>
> Key: APEXMALHAR-2373
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2373
> Project: Apache Apex Malhar
> Issue Type: Bug
>Reporter: Bhupesh Chawda
> Assignee: Dongming Liang
>
> Database: Oracle
> Column type NUMERIC gives following exception in JdbcPOJOInsertOutputOperator:
> 2016-12-19 18:42:26,032 DEBUG jdbc.JdbcPOJOInsertOutputOperator
> (JdbcPOJOInsertOutputOperator.java:populateColumnDataTypes(162)) - resultSet
> MetaData column count 3
> 2016-12-19 18:42:26,033 DEBUG jdbc.JdbcPOJOInsertOutputOperator
> (JdbcPOJOInsertOutputOperator.java:populateColumnDataTypes(170)) - column
> name ACCOUNT_NO type 2
> 2016-12-19 18:42:26,033 DEBUG jdbc.JdbcPOJOInsertOutputOperator
> (JdbcPOJOInsertOutputOperator.java:populateColumnDataTypes(170)) - column
> name NAME type 12
> 2016-12-19 18:42:26,033 DEBUG jdbc.JdbcPOJOInsertOutputOperator
> (JdbcPOJOInsertOutputOperator.java:populateColumnDataTypes(170)) - column
> name AMOUNT type 2
> 2016-12-19 18:42:26,033 DEBUG engine.StreamingContainer
> (StreamingContainer.java:setupNode(1333)) - activating 2 in container
> container_e15_1482167280022_0017_01_02
> 2016-12-19 18:42:26,033 DEBUG jdbc.JdbcPOJOInsertOutputOperator
> (JdbcPOJOInsertOutputOperator.java:activate(134)) - insert statement is
> INSERT INTO test_output_event_table (ACCOUNT_NO,NAME,AMOUNT) VALUES (?,?,?)
> 2016-12-19 18:42:26,034 ERROR engine.StreamingContainer
> (StreamingContainer.java:run(1431)) - Abandoning deployment of operator
> OperatorDeployInfo[id=2,name=JdbcOutput,type=GENERIC,checkpoint={,
> 0,
> 0},inputs=[OperatorDeployInfo.InputDeployInfo[portName=input,streamId=POJO's,sourceNodeId=1,sourcePortName=outputPort,locality=CONTAINER_LOCAL,partitionMask=0,partitionKeys=]],outputs=[]]
> due to setup failure.
> java.lang.RuntimeException: unsupported data type 2
> at
> com.datatorrent.lib.db.jdbc.AbstractJdbcPOJOOutputOperator.handleUnknownDataType(AbstractJdbcPOJOOutputOperator.java:177)
> at
> com.datatorrent.lib.db.jdbc.AbstractJdbcPOJOOutputOperator.activate(AbstractJdbcPOJOOutputOperator.java:292)
> at
> com.datatorrent.lib.db.jdbc.JdbcPOJOInsertOutputOperator.activate(JdbcPOJOInsertOutputOperator.java:136)
> at
> com.datatorrent.lib.db.jdbc.JdbcPOJOInsertOutputOperator.activate(JdbcPOJOInsertOutputOperator.java:47)
> at com.datatorrent.stram.engine.Node.activate(Node.java:619)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (APEXMALHAR-2239) Null pointer exception in JDBCPojoInputOperator is thrown when we set a query to fetch rows and have additional columns in fieldInfos
[ https://issues.apache.org/jira/browse/APEXMALHAR-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15878743#comment-15878743 ] Dongming Liang commented on APEXMALHAR-2239: [~Hitesh_]I'll work on the comments today. > Null pointer exception in JDBCPojoInputOperator is thrown when we set a query > to fetch rows and have additional columns in fieldInfos > - > > Key: APEXMALHAR-2239 > URL: https://issues.apache.org/jira/browse/APEXMALHAR-2239 > Project: Apache Apex Malhar > Issue Type: Bug >Affects Versions: 3.5.0 >Reporter: Venkatesh Kottapalli > Assignee: Dongming Liang >Priority: Minor > Attachments: testJdbcPojoInputOperator.txt > > > The following exception is thrown in JDBCPojoInputOperator when the field > names for the table provided in the FieldInfo mapping don't match with the > column names of the table. > Exception: > Abandoning deployment due to setup failure. java.lang.NullPointerException > at > com.datatorrent.lib.db.jdbc.JdbcPOJOInputOperator.activate(JdbcPOJOInputOperator.java:366) > at > com.datatorrent.lib.db.jdbc.JdbcPOJOInputOperator.activate(JdbcPOJOInputOperator.java:67) > at com.datatorrent.stram.engine.Node.activate(Node.java:619) > at > com.datatorrent.stram.engine.StreamingContainer.setupNode(StreamingContainer.java:1336) > at > com.datatorrent.stram.engine.StreamingContainer.access$100(StreamingContainer.java:130) > at > com.datatorrent.stram.engine.StreamingContainer$2.run(StreamingContainer.java:1388) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (APEXMALHAR-2239) Null pointer exception in JDBCPojoInputOperator when the field names do not match in Pojo, table
[
https://issues.apache.org/jira/browse/APEXMALHAR-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843119#comment-15843119
]
Dongming Liang commented on APEXMALHAR-2239:
[~Hitesh_]I do need some help. I'm not sure if the following will reproduce the
problem. I tried to change the column name
in JdbcPojoOperatorTest.java
from STARTDATE to STARTDATE1
fieldInfos.add(new FieldInfo("STARTDATE1", "startDate1", null));
It gives a different error though:
java.lang.RuntimeException: java.sql.SQLSyntaxErrorException: user lacks
privilege or object not found: STARTDATE1
at
com.datatorrent.lib.db.jdbc.JdbcPOJOInputOperator.setup(JdbcPOJOInputOperator.java:147)
at
com.datatorrent.lib.db.jdbc.JdbcPojoOperatorTest.testJdbcPojoInputOperator(JdbcPojoOperatorTest.java:635)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at org.junit.runner.JUnitCore.run(JUnitCore.java:160)
at
com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:69)
at
com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:234)
at
com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:74)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
Caused by: java.sql.SQLSyntaxErrorException: user lacks privilege or object not
found: STARTDATE1
at org.hsqldb.jdbc.JDBCUtil.sqlException(Unknown Source)
at org.hsqldb.jdbc.JDBCUtil.sqlException(Unknown Source)
at org.hsqldb.jdbc.JDBCPreparedStatement.(Unknown Source)
at org.hsqldb.jdbc.JDBCConnection.prepareStatement(Unknown Source)
at
com.datatorrent.lib.db.jdbc.JdbcPOJOInputOperator.setup(JdbcPOJOInputOperator.java:142)
... 28 more
Could you advise if this the right way to investigate?
> Null pointer exception in JDBCPojoInputOperator when the field names do not
> match in Pojo, table
>
>
> Key: APEXMALHAR-2239
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2239
> Project: Apache Apex Malhar
> Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Venkatesh Kottapalli
>Assignee: Dongming Liang
>Priority: Minor
>
> The following exception is thrown in JDBCPojoInputOperator when the field
> names for the table provided in the FieldInfo mapping don't match with the
> column names of the table.
> Exception:
> Abandoning deployment due to setup failure. java.lang.NullPointerException
> at
> com.datatorrent.lib.db.jdbc.JdbcPOJOInputOperator.activate(JdbcPOJOInputOperator.java:366)
> at
> com.datatorrent.lib.db.jdbc.JdbcPOJOInputOperator.activate(JdbcPOJOInputOperator.java:67)
> at com.datatorrent.stram.engine.Node.activate(Node.java:619)
> at
> com.datatorrent.stram.engine.StreamingContainer.setupNode(StreamingContainer.java:1336)
>
[jira] [Commented] (APEXMALHAR-2239) Null pointer exception in JDBCPojoInputOperator when the field names do not match in Pojo, table
[ https://issues.apache.org/jira/browse/APEXMALHAR-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15805226#comment-15805226 ] Dongming Liang commented on APEXMALHAR-2239: [~Venkatesh Kottapalli]I"d like to work on this. Do you have a test case available? Thanks. > Null pointer exception in JDBCPojoInputOperator when the field names do not > match in Pojo, table > > > Key: APEXMALHAR-2239 > URL: https://issues.apache.org/jira/browse/APEXMALHAR-2239 > Project: Apache Apex Malhar > Issue Type: Bug >Affects Versions: 3.5.0 >Reporter: Venkatesh Kottapalli >Assignee: Dongming Liang >Priority: Minor > > The following exception is thrown in JDBCPojoInputOperator when the field > names for the table provided in the FieldInfo mapping don't match with the > column names of the table. > Exception: > Abandoning deployment due to setup failure. java.lang.NullPointerException > at > com.datatorrent.lib.db.jdbc.JdbcPOJOInputOperator.activate(JdbcPOJOInputOperator.java:366) > at > com.datatorrent.lib.db.jdbc.JdbcPOJOInputOperator.activate(JdbcPOJOInputOperator.java:67) > at com.datatorrent.stram.engine.Node.activate(Node.java:619) > at > com.datatorrent.stram.engine.StreamingContainer.setupNode(StreamingContainer.java:1336) > at > com.datatorrent.stram.engine.StreamingContainer.access$100(StreamingContainer.java:130) > at > com.datatorrent.stram.engine.StreamingContainer$2.run(StreamingContainer.java:1388) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (APEXMALHAR-2239) Null pointer exception in JDBCPojoInputOperator when the field names do not match in Pojo, table
[ https://issues.apache.org/jira/browse/APEXMALHAR-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dongming Liang reassigned APEXMALHAR-2239: -- Assignee: Dongming Liang > Null pointer exception in JDBCPojoInputOperator when the field names do not > match in Pojo, table > > > Key: APEXMALHAR-2239 > URL: https://issues.apache.org/jira/browse/APEXMALHAR-2239 > Project: Apache Apex Malhar > Issue Type: Bug >Affects Versions: 3.5.0 >Reporter: Venkatesh Kottapalli > Assignee: Dongming Liang >Priority: Minor > > The following exception is thrown in JDBCPojoInputOperator when the field > names for the table provided in the FieldInfo mapping don't match with the > column names of the table. > Exception: > Abandoning deployment due to setup failure. java.lang.NullPointerException > at > com.datatorrent.lib.db.jdbc.JdbcPOJOInputOperator.activate(JdbcPOJOInputOperator.java:366) > at > com.datatorrent.lib.db.jdbc.JdbcPOJOInputOperator.activate(JdbcPOJOInputOperator.java:67) > at com.datatorrent.stram.engine.Node.activate(Node.java:619) > at > com.datatorrent.stram.engine.StreamingContainer.setupNode(StreamingContainer.java:1336) > at > com.datatorrent.stram.engine.StreamingContainer.access$100(StreamingContainer.java:130) > at > com.datatorrent.stram.engine.StreamingContainer$2.run(StreamingContainer.java:1388) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (APEXMALHAR-2220) Move the FunctionOperator to Malhar library
[ https://issues.apache.org/jira/browse/APEXMALHAR-2220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15572382#comment-15572382 ] Dongming Liang commented on APEXMALHAR-2220: [~siyuan] Did you have a chance to look into my question above? Thanks. > Move the FunctionOperator to Malhar library > --- > > Key: APEXMALHAR-2220 > URL: https://issues.apache.org/jira/browse/APEXMALHAR-2220 > Project: Apache Apex Malhar > Issue Type: Improvement >Reporter: Siyuan Hua > Assignee: Dongming Liang > > FunctionOperator initially is just designed for high-level API and we think > it can also useful if people want to build stateless transformation and work > with other operator directly. FunctionOperator can be reused. Thus we should > move FO to malhar library -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [VOTE] Hadoop upgrade
+1 for 2.6.x Best Regards, - Dongming Dongming Liang dongming.li...@gmail.com On Oct 5, 2016 11:17 AM, "Sanjay Pujare" <san...@datatorrent.com> wrote: > +1 for 2.6 > > > On Wed, Oct 5, 2016 at 11:52 AM, Pradeep Kumbhar <prad...@datatorrent.com> > wrote: > > > +1 for 2.6 > > > > On Tue, Oct 4, 2016 at 8:42 PM, Munagala Ramanath <r...@datatorrent.com> > > wrote: > > > > > +1 for 2.6.x > > > > > > Ram > > > > > > On Mon, Oct 3, 2016 at 1:47 PM, David Yan <da...@datatorrent.com> > wrote: > > > > > > > Hi all, > > > > > > > > Thomas created this ticket for upgrading our Hadoop dependency > version > > a > > > > couple weeks ago: > > > > > > > > https://issues.apache.org/jira/browse/APEXCORE-536 > > > > > > > > We'd like to get the ball rolling and would like to take a vote from > > the > > > > community which version we would like to upgrade to. We have these > > > choices: > > > > > > > > 2.2.0 (no upgrade) > > > > 2.4.x > > > > 2.5.x > > > > 2.6.x > > > > > > > > We are not considering 2.7.x because we already know that many Apex > > users > > > > are using Hadoop distros that are based on 2.6. > > > > > > > > Please note that Apex works with all versions of Hadoop higher or > equal > > > to > > > > the Hadoop version Apex depends on, as long as it's 2.x.x. We are not > > > > considering Hadoop 3.0.0-alpha yet at this time. > > > > > > > > When voting, please keep these in mind: > > > > > > > > - The features that are added in 2.4.x, 2.5.x, and 2.6.x > respectively, > > > and > > > > how useful those features are for Apache Apex > > > > - The Hadoop versions the major distros (Cloudera, Hortonworks, MapR, > > > EMR, > > > > etc) are supporting > > > > - The Hadoop versions what typical Apex users are using > > > > > > > > Thanks, > > > > > > > > David > > > > > > > > > > > > > > > -- > > *regards,* > > *~pradeep* > > >
[jira] [Commented] (APEXMALHAR-2220) Move the FunctionOperator to Malhar library
[ https://issues.apache.org/jira/browse/APEXMALHAR-2220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15545968#comment-15545968 ] Dongming Liang commented on APEXMALHAR-2220: [~hsy541] There seems to be a circular dependency problem if we move them to org.apache.apex.malhar.lib it (malhar-library) depends on malhar-stream, however at the same time malhar-stream depends on malhar-library How about we merge them under org.apache.apex.malhar.lib in malhar-stream? > Move the FunctionOperator to Malhar library > --- > > Key: APEXMALHAR-2220 > URL: https://issues.apache.org/jira/browse/APEXMALHAR-2220 > Project: Apache Apex Malhar > Issue Type: Improvement >Reporter: Siyuan Hua > Assignee: Dongming Liang > > FunctionOperator initially is just designed for high-level API and we think > it can also useful if people want to build stateless transformation and work > with other operator directly. FunctionOperator can be reused. Thus we should > move FO to malhar library -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (APEXMALHAR-2220) Move the FunctionOperator to Malhar library
[ https://issues.apache.org/jira/browse/APEXMALHAR-2220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15542762#comment-15542762 ] Dongming Liang commented on APEXMALHAR-2220: [~siyuan]I'm not sure where we should merge them into. Should it be a new package? Or should we put them under somewhere under "com.datatorrent.lib.stream"? Please clarify. Thanks! > Move the FunctionOperator to Malhar library > --- > > Key: APEXMALHAR-2220 > URL: https://issues.apache.org/jira/browse/APEXMALHAR-2220 > Project: Apache Apex Malhar > Issue Type: Improvement >Reporter: Siyuan Hua >Assignee: Dongming Liang > > FunctionOperator initially is just designed for high-level API and we think > it can also useful if people want to build stateless transformation and work > with other operator directly. FunctionOperator can be reused. Thus we should > move FO to malhar library -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [ANNOUNCE] New Apache Apex PMC Member: Chandni Singh
Congrats, Chandni! Thanks, - Dongming Dongming LIANG dongming.li...@gmail.com On Mon, Sep 12, 2016 at 11:28 AM, Pradeep A. Dalvi <p...@apache.org> wrote: > Congratulations, Chandni! > > Thanks, > Pradeep A. Dalvi > > On Mon, Sep 12, 2016 at 9:33 AM, Thomas Weise <t...@apache.org> wrote: > > > The Apache Apex PMC is pleased to announce that Chandni Singh is now a > PMC > > member. We appreciate all her contributions to the project so far, and > are > > looking forward to more. > > > > Congrats Chandni! > > Thomas, for the Apache Apex PMC. > > >
Re: Megh operator library
+1 for me. Thanks, - Dongming Dongming LIANG dongming.li...@gmail.com On Thu, Sep 8, 2016 at 9:02 PM, Devendra Tagare <devend...@datatorrent.com> wrote: > Hi, > > Count me in for one operator as well. > > Thanks, > Dev > > On Fri, Sep 9, 2016 at 8:33 AM, Yogi Devendra < > devendra.vyavah...@gmail.com> > wrote: > > > Hi, > > > > I would like to contribute for this effort for one operator. Please count > > me in for this effort. > > > > ~ Yogi > > > > On 9 September 2016 at 03:10, Pramod Immaneni <pra...@datatorrent.com> > > wrote: > > > > > Hi, > > > > > > DataTorrent, the initial contributor to Apex and the company I work > for, > > > has opened up a library of operators called Megh recently to the public > > and > > > has made the repository available under the Apache License. The link to > > the > > > repository is below. These operators, for the most part, contain > > > functionality that is complementary to what Malhar library provides and > > > were developed to solve business use cases that arose over time. Also, > > some > > > operators in Malhar were inspired from early implementations in the > Megh > > > library and were built upon knowledge gained in doing the original > > > implementations. > > > > > > Our goal is to not have Megh as a separate library but rather bring > these > > > operators into Malhar in a fashion that it is consistent with the > Malhar > > > project and repository. In the upcoming days, in a gradual fashion, we > > will > > > have more details on the individual operators that we would like to > > > contribute. Also, if you are interested in helping with this effort > > please > > > raise your hand. > > > > > > https://github.com/DataTorrent/Megh/ > > > > > > Thanks > > > > > >
Re: [ANNOUNCE] New Apache Apex PMC Member: Siyuan Hua
Congrats, Siyuan! Thanks, - Dongming Dongming LIANG dongming.li...@gmail.com On Thu, Jun 16, 2016 at 12:19 AM, Shubham Pathak <shub...@datatorrent.com> wrote: > Congrats Siyuan ! > > Thanks, > Shubham > > On Thu, Jun 16, 2016 at 11:17 AM, Ashish Tadose <ashishtad...@gmail.com> > wrote: > > > Congratulations Siyuan. > > > > Ashish > > > > > On 16-Jun-2016, at 10:49 AM, Aniruddha Thombare < > > anirud...@datatorrent.com> wrote: > > > > > > Congratulations!!! > > > > > > Thanks, > > > > > > A > > > > > > _ > > > Sent with difficulty, I mean handheld ;) > > > On 16 Jun 2016 10:47 am, "Devendra Tagare" <devend...@datatorrent.com> > > > wrote: > > > > > >> Congratulations Siyuan > > >> > > >> Cheers, > > >> Dev > > >> On Jun 15, 2016 10:13 PM, "Chinmay Kolhatkar" < > chin...@datatorrent.com> > > >> wrote: > > >> > > >>> Congrats Siyuan :) > > >>> > > >>> On Wed, Jun 15, 2016 at 10:05 PM, Priyanka Gugale <pri...@apache.org > > > > >>> wrote: > > >>> > > >>>> Congrats Siyuan :) > > >>>> > > >>>> -Priyanka > > >>>> > > >>>> On Thu, Jun 16, 2016 at 10:19 AM, Pradeep Kumbhar < > > >>> prad...@datatorrent.com > > >>>>> > > >>>> wrote: > > >>>> > > >>>>> Congratulations Siyuan!! > > >>>>> > > >>>>> On Thu, Jun 16, 2016 at 10:17 AM, Teddy Rusli < > te...@datatorrent.com > > >>> > > >>>>> wrote: > > >>>>> > > >>>>>> Congrats Siyuan! > > >>>>>> > > >>>>>> On Wed, Jun 15, 2016 at 9:28 PM, Ashwin Chandra Putta < > > >>>>>> ashwinchand...@gmail.com> wrote: > > >>>>>> > > >>>>>>> Congratulations Siyuan!! > > >>>>>>> On Jun 15, 2016 9:26 PM, "Thomas Weise" <tho...@datatorrent.com> > > >>>>> wrote: > > >>>>>>> > > >>>>>>>> The Apache Apex PMC is pleased to announce that Siyuan Hua is > > >>> now a > > >>>>> PMC > > >>>>>>>> member. We appreciate all his contributions to the project so > > >>> far, > > >>>>> and > > >>>>>>> are > > >>>>>>>> looking forward to more. > > >>>>>>>> > > >>>>>>>> Welcome, Siyuan, and congratulations! > > >>>>>>>> Thomas, for the Apache Apex PMC. > > >>>>>>>> > > >>>>>>> > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>>> -- > > >>>>>> Regards, > > >>>>>> > > >>>>>> Teddy Rusli > > >>>>>> > > >>>>> > > >>>>> > > >>>>> > > >>>>> -- > > >>>>> *regards,* > > >>>>> *~pradeep* > > >>>>> > > >>>> > > >>> > > >> > > > > >
