The Maven artifacts are for development. There is no need to install
anything separately when developing Apex applications, including the
testing in embedded mode.
An installation is needed to launch applications on the cluster and the
options I mentioned are for that. Have not seen users asking f
Hi Hitesh,
Are you suggest the build scripts of apex should create a convenient binary
package (maybe just a tarball) which is directly deploy-able?
- Chinmay.
On Thu, Mar 3, 2016 at 3:04 AM, Hitesh Shah wrote:
> I am not sure if that is entirely accurate. Convenience binaries usually
> refer
For new code we should use org.apache.apex
I prefer not to use "module" in the package name but keep them together
with related operators (modules and operators are not different from users
perspective).
On Wed, Mar 2, 2016 at 9:59 PM, Chinmay Kolhatkar
wrote:
> +1 for seperate namespace for mo
+1 for seperate namespace for modules.
On Thu, Mar 3, 2016 at 10:58 AM, Priyanka Gugale
wrote:
> That is also a option but then I have a question, do we want to treat
> modules separately or it is just a type of operator, may be a super
> operator?
> Also I believe it would be good if we have fe
[
https://issues.apache.org/jira/browse/APEXMALHAR-1968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bhupesh Chawda closed APEXMALHAR-1968.
--
Releasing Apache Apex Malhar 3.3.1-incubating
> Update NOTICE copyright year
> ---
[
https://issues.apache.org/jira/browse/APEXMALHAR-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bhupesh Chawda closed APEXMALHAR-2003.
--
Releasing Apache Apex Malhar 3.3.1-incubating
> NPE in FileSplitterInput
> ---
[
https://issues.apache.org/jira/browse/APEXMALHAR-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bhupesh Chawda closed APEXMALHAR-1993.
--
Releasing Apache Apex Malhar 3.3.1-incubating
> Committed offsets are not present in o
[
https://issues.apache.org/jira/browse/APEXMALHAR-1984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bhupesh Chawda closed APEXMALHAR-1984.
--
Releasing Apache Apex Malhar 3.3.1-incubating
> Operators that use Kryo directly would
[
https://issues.apache.org/jira/browse/APEXMALHAR-1994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bhupesh Chawda closed APEXMALHAR-1994.
--
Releasing Apache Apex Malhar 3.3.1-incubating
> Operator partitions are reporting offs
[
https://issues.apache.org/jira/browse/APEXMALHAR-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bhupesh Chawda closed APEXMALHAR-1990.
--
Releasing Apache Apex Malhar 3.3.1-incubating
> Occasional concurrent modification exc
[
https://issues.apache.org/jira/browse/APEXMALHAR-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bhupesh Chawda closed APEXMALHAR-1983.
--
Releasing Apache Apex Malhar 3.3.1-incubating
> Support special chars in topics settin
[
https://issues.apache.org/jira/browse/APEXMALHAR-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bhupesh Chawda closed APEXMALHAR-1998.
--
Releasing Apache Apex Malhar 3.3.1-incubating
> Kafka unit test memory requirement bre
[
https://issues.apache.org/jira/browse/APEXMALHAR-1970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bhupesh Chawda closed APEXMALHAR-1970.
--
Releasing Apache Apex Malhar 3.3.1-incubating
> ArrayOutOfBoundary error in One_To_Man
[
https://issues.apache.org/jira/browse/APEXMALHAR-1973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bhupesh Chawda closed APEXMALHAR-1973.
--
Releasing Apache Apex Malhar 3.3.1-incubating
> InitialOffset bug and duplication caus
[
https://issues.apache.org/jira/browse/APEXMALHAR-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bhupesh Chawda closed APEXMALHAR-1986.
--
Releasing Apache Apex Malhar 3.3.1-incubating
> Change semantic version check to use 3
That is also a option but then I have a question, do we want to treat
modules separately or it is just a type of operator, may be a super
operator?
Also I believe it would be good if we have feature wise packages than using
our custom terms to create package, so anyone can easily locate the classes
The main purpose is not to handle back pressure but to limit bandwidth
usage by applications. This is useful in ingestion use cases. Typically
user needs to ingest say up to 1GB per sec and not more. The tuple size
may vary based on messages based tuples (few KBs) or block tuples for files
(few MB
[
https://issues.apache.org/jira/browse/APEXCORE-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15176963#comment-15176963
]
ASF GitHub Bot commented on APEXCORE-10:
Github user ishark commented on the pull
Github user ishark commented on the pull request:
https://github.com/apache/incubator-apex-core/pull/250#issuecomment-191536790
Testing Done:
1. Unit tests for Dag Validation scenarios
2. Unit tests for host allocation based on affinity rules
3. Tested following scena
[
https://issues.apache.org/jira/browse/APEXCORE-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15176959#comment-15176959
]
ASF GitHub Bot commented on APEXCORE-10:
Github user ishark commented on the pull
Github user ishark commented on the pull request:
https://github.com/apache/incubator-apex-core/pull/250#issuecomment-191536088
@tweise Pleas review
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does no
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-apex-core/pull/257
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the fe
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-apex-core/pull/255
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the fe
Github user tweise commented on a diff in the pull request:
https://github.com/apache/incubator-apex-core/pull/257#discussion_r54800888
--- Diff:
engine/src/test/resources/testConfigPackage/testConfigPackageSrc/META-INF/MANIFEST.MF
---
@@ -1,16 +1,15 @@
-Manifest-Version: 1.0
Vlad Rozov created APEXCORE-373:
---
Summary: Create unit test for the case when tuple length exceeds
data list buffer block size
Key: APEXCORE-373
URL: https://issues.apache.org/jira/browse/APEXCORE-373
P
GitHub user vrozov opened a pull request:
https://github.com/apache/incubator-apex-core/pull/257
Fixed EOL
@davidyan74 Please merge
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vrozov/incubator-apex-core EOL
Alternatively you
I am not sure if that is entirely accurate. Convenience binaries usually refer
to a final assembled/package bundle that can be deployed in the end-user env.
thanks
— Hitesh
On Mar 2, 2016, at 11:51 AM, Thomas Weise wrote:
> Binaries are the jar files in Maven. For the Apex developer, everythi
Getting close:
https://github.com/tweise/incubator-apex-core/tree/APEXCORE-293/docs
Will probably be merged in a day or two.
On Wed, Mar 2, 2016 at 11:46 AM, P. Taylor Goetz wrote:
> Not explicitly called out in the maturity model, but also the Apex
> documentation needs to be moved off of data
Binaries are the jar files in Maven. For the Apex developer, everything is
driven through Maven, starting from the archetype.
Explicit install is only needed for the CLI. Following are the available
options:
- Checkout from git: https://github.com/apache
/incubator-apex-core/blob/5f216a1bd27
Not explicitly called out in the maturity model, but also the Apex
documentation needs to be moved off of datatorrent.com and onto ASF
infrastructure. It also would need to be stripped of any references to
proprietary datatorrent software.
What’s the status of that effort?
-Taylor
> On Mar 2,
[
https://issues.apache.org/jira/browse/APEXCORE-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15176302#comment-15176302
]
ASF GitHub Bot commented on APEXCORE-365:
-
Github user vrozov commented on the p
Github user vrozov commented on the pull request:
https://github.com/apache/incubator-apex-core/pull/256#issuecomment-191387488
Will file JIRA to add a unit test to cover the use case to the buffer
server suite.
---
If your project is set up for it, you can reply to this email and h
Not sure if this is helpful, but there is already a utility in Malhar for
converting tuples per second to tuples per window. This allows the user to
define a property in tuples per second, then the operator can convert that
to tuples per window so it emits the correct number of tuples per window.
My vote is to have a separate namespace for modules.
Is it time to introduce
org.apache.apex.module.io.fs ?
On Wed, Mar 2, 2016 at 3:25 AM Priyanka Gugale
wrote:
> I am planning to put this module in malhar-library project in
> package: com.datatorrent.lib.io.fs
> Let me know if this is accepta
Hi Priyanka,
Indeed this is a useful feature.
I believe number bytes consumed per sec can as well translate to number of
tuples consumed per sec.
If above is correct, won't back pressure that is handled by bufferserver
help in your use case?
Thanks,
Chinmay.
On 2 Mar 2016 4:49 p.m., "Priyanka G
I believe RE40 is still pending?
— Hitesh
On Mar 2, 2016, at 1:38 AM, Chinmay Kolhatkar wrote:
> Hello Community,
>
> We've created an initial project maturity model on apex website:
> http://apex.incubator.apache.org/maturity.html
>
> This model is based on based on ASF project maturity mod
[
https://issues.apache.org/jira/browse/APEXCORE-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15176142#comment-15176142
]
ASF GitHub Bot commented on APEXCORE-365:
-
Github user asfgit closed the pull re
I see. You're right. The "who we are" info is effectively only on the
incubation status page right now, which is not something that would be
maintained after incubation.
http://incubator.apache.org/projects/apex.html
Thanks for the reply. I think addressing those 2 items would resolve CO10.
Chris,
I can think of 2 items:
- Version compatibility
- Who we are page
Do you see anything else?
Thanks,
Thomas
On Wed, Mar 2, 2016 at 10:18 AM, Chris Nauroth
wrote:
> This looks great! I know some IPMC members will appreciate that you've
> documented this and can reference it in a grad
[
https://issues.apache.org/jira/browse/APEXCORE-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Weise updated APEXCORE-365:
--
Summary: Buffer server handling for tuple length that exceeds data list
block size (was: Log
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-apex-core/pull/256
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the fe
This looks great! I know some IPMC members will appreciate that you've
documented this and can reference it in a graduation discussion.
I see a red cross next to CO10: The project has a well-known homepage that
points to all the information required to operate according to this
maturity model. W
[
https://issues.apache.org/jira/browse/APEXCORE-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15176074#comment-15176074
]
ASF GitHub Bot commented on APEXCORE-365:
-
GitHub user vrozov opened a pull requ
GitHub user vrozov opened a pull request:
https://github.com/apache/incubator-apex-core/pull/256
APEXCORE-365 - Adjust size for the VarInt length
@tweise Please merge.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vrozov/incubat
For QU40 we still need to add the page documenting compatibility:
https://issues.apache.org/jira/browse/APEXCORE-319
On Wed, Mar 2, 2016 at 1:38 AM, Chinmay Kolhatkar
wrote:
> Hello Community,
>
> We've created an initial project maturity model on apex website:
> http://apex.incubator.apache.o
Github user tweise commented on a diff in the pull request:
https://github.com/apache/incubator-apex-malhar/pull/205#discussion_r54749020
--- Diff:
kafka/src/main/java/org/apache/apex/malhar/kafka/AbstractKafkaInputOperator.java
---
@@ -339,6 +394,11 @@ public void
assign(Set as
[
https://issues.apache.org/jira/browse/APEXCORE-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15175799#comment-15175799
]
Pramod Immaneni commented on APEXCORE-339:
--
For input operators same data in sa
[
https://issues.apache.org/jira/browse/APEXCORE-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15175797#comment-15175797
]
Pramod Immaneni commented on APEXCORE-339:
--
We need a way to identify an operat
I am planning to put this module in malhar-library project in
package: com.datatorrent.lib.io.fs
Let me know if this is acceptable?
-Priyanka
On Tue, Feb 23, 2016 at 6:45 PM, Priyanka Gugale
wrote:
> I haven't created any branch yet, should share it with you as soon as I
> add the code for modu
Github user chaithu14 commented on a diff in the pull request:
https://github.com/apache/incubator-apex-malhar/pull/205#discussion_r54710624
--- Diff:
kafka/src/main/java/org/apache/apex/malhar/kafka/AbstractKafkaInputOperator.java
---
@@ -339,6 +394,11 @@ public void
assign(Set
Many times we need to put bandwidth restrictions or put some limit on input
operator for number of bytes to be consumed per second. As I understand in
Apex there is no direct support for this feature.
I am planning to write a bandwidth manager which will help in limiting
bandwidth at Input operato
Github user chaithu14 commented on a diff in the pull request:
https://github.com/apache/incubator-apex-malhar/pull/205#discussion_r54710284
--- Diff:
kafka/src/main/java/org/apache/apex/malhar/kafka/AbstractKafkaInputOperator.java
---
@@ -339,6 +394,11 @@ public void
assign(Set
Github user chaithu14 commented on a diff in the pull request:
https://github.com/apache/incubator-apex-malhar/pull/205#discussion_r54709695
--- Diff:
kafka/src/main/java/org/apache/apex/malhar/kafka/KafkaConsumerWrapper.java ---
@@ -137,6 +189,9 @@ public void run()
Priyanka Gugale created APEXMALHAR-2008:
---
Summary: Create hdfs file input module
Key: APEXMALHAR-2008
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2008
Project: Apache Apex Malhar
Hello Community,
We've created an initial project maturity model on apex website:
http://apex.incubator.apache.org/maturity.html
This model is based on based on ASF project maturity model.
On the webpage, green check icon next to the element means it is achieved.
Red cross icon mean, its not ach
55 matches
Mail list logo
