from:"brightchen"

[GitHub] apex-malhar pull request #320: APEXMALHAR-2120 #resolve #comment solve probl...

2016-06-16 Thread brightchen

Github user brightchen closed the pull request at:

https://github.com/apache/apex-malhar/pull/320


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #321: APEXMALHAR-2120 #resolve #comment solve probl...

2016-06-16 Thread brightchen

GitHub user brightchen opened a pull request:

https://github.com/apache/apex-malhar/pull/321

APEXMALHAR-2120 #resolve #comment solve problems of KafkaInputOperatoâ¦

â¦rTest and AbstractKafkaInputOperator

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2120

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/321.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #321


commit 22e0fad933f560b19379cc22d4bda12b2da90b79
Author: brightchen <bri...@datatorrent.com>
Date:   2016-06-14T23:30:17Z

APEXMALHAR-2120 #resolve #comment solve problems of KafkaInputOperatorTest 
and AbstractKafkaInputOperator




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #321: APEXMALHAR-2120 #resolve #comment solve probl...

2016-06-22 Thread brightchen

GitHub user brightchen reopened a pull request:

https://github.com/apache/apex-malhar/pull/321

APEXMALHAR-2120 #resolve #comment solve problems of KafkaInputOperatoâ¦

â¦rTest and AbstractKafkaInputOperator

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2120

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/321.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #321


commit 252a70127dbcec3b462ccb714f13a5c7684e4293
Author: brightchen <bri...@datatorrent.com>
Date:   2016-06-14T23:30:17Z

APEXMALHAR-2120 #resolve #comment solve problems of KafkaInputOperatorTest 
and AbstractKafkaInputOperator




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #321: APEXMALHAR-2120 #resolve #comment solve probl...

2016-06-20 Thread brightchen

Github user brightchen commented on a diff in the pull request:

https://github.com/apache/apex-malhar/pull/321#discussion_r67763344
  
--- Diff: 
kafka/src/test/java/org/apache/apex/malhar/kafka/KafkaInputOperatorTest.java ---
@@ -68,26 +70,53 @@
 
   public static String APPLICATION_PATH = baseDir + File.separator + 
StramLocalCluster.class.getName() + File.separator;
 
+  public class KafkaTestInfo extends TestWatcher
+  {
+public org.junit.runner.Description desc;
+
+public String getDir()
+{
+  String methodName = desc.getMethodName();
+  String className = desc.getClassName();
+  return "target/" + className + "/" + methodName + "/" + testName;
+}
+
+@Override
+protected void starting(org.junit.runner.Description description)
+{
+  this.desc = description;
+}
+  }
+  
+  @Rule
+  public final KafkaTestInfo testInfo = new KafkaTestInfo();
+  
+  
   @Parameterized.Parameters(name = "multi-cluster: {0}, multi-partition: 
{1}, partition: {2}")
   public static Collection<Object[]> testScenario()
   {
-return Arrays.asList(new Object[][]{{true, false, "one_to_one"},// 
multi cluster with single partition
+return Arrays.asList(new Object[][]{
+  {true, false, "one_to_one"},// multi cluster with single partition
   {true, false, "one_to_many"},
   {true, true, "one_to_one"},// multi cluster with multi partitions
-  {true, true, "one_to_many"},
+  {true, true, "one_to_many"},   //test failed, no data received.
   {false, true, "one_to_one"}, // single cluster with multi partitions
-  {false, true, "one_to_many"},
+  {false, true, "one_to_many"},  //test failed, no data received.
   {false, false, "one_to_one"}, // single cluster with single 
partitions
   {false, false, "one_to_many"}
 });
   }
 
+
+
   @Before
   public void before()
   {
-FileUtils.deleteQuietly(new File(APPLICATION_PATH));
-tupleCollection.clear();
+//FileUtils.deleteQuietly(new File(APPLICATION_PATH));
--- End diff --

The different test case/test Scenario use difference directory. So it is 
not necessary to delete the directory


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #321: APEXMALHAR-2120 #resolve #comment solve probl...

2016-06-20 Thread brightchen

Github user brightchen commented on a diff in the pull request:

https://github.com/apache/apex-malhar/pull/321#discussion_r67763894
  
--- Diff: 
kafka/src/test/java/org/apache/apex/malhar/kafka/KafkaInputOperatorTest.java ---
@@ -275,10 +324,21 @@ public void testInputOperator(boolean hasFailure, 
boolean idempotent) throws Exc
 final LocalMode.Controller lc = lma.getController();
 lc.setHeartbeatMonitoringEnabled(false);
 
-lc.runAsync();
--- End diff --

I added a monitor thread to make sure the Engine will be complete shutdown 
before start next test case


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #316: High-level WindowedStream API (Review only)

2016-06-20 Thread brightchen

Github user brightchen commented on a diff in the pull request:

https://github.com/apache/apex-malhar/pull/316#discussion_r67746283
  
--- Diff: 
library/src/main/java/com/datatorrent/lib/window/WindowOption.java ---
@@ -0,0 +1,143 @@
+package com.datatorrent.lib.window;
+
+import java.util.LinkedList;
+import java.util.List;
+
+/**
+ *
+ */
+public abstract class WindowOption
+{
+
+  private TriggerOption[] triggerOptions;
+
+  private AccumulationMode accumulationMode = AccumulationMode.ACCUMULATE;
+
+  private List<Object[]> lateness = new LinkedList<>();
+
+  public static enum AccumulationMode
+  {
+DISCARD,
+ACCUMULATE,
+ACCUMULATE_DELTA
+  }
+
+  public static class GlobalWindow extends WindowOption
+  {
+
+  }
+
+  public static class FixedWindow extends WindowOption
+  {
+FixedWindow(long quantity, Quantification.Unit unit)
+{
+  size.add(new Object[]{quantity, unit});
+}
+
+FixedWindow(List<Object[]> size)
+{
+  this.size = size;
+}
+
+private List<Object[]> size = new LinkedList<>();
+
+public SlidingWindow slideBy(long slidingQuantity, Quantification.Unit 
slidingUnit)
+{
+  SlidingWindow sw = new SlidingWindow(this.size);
+  sw.delta.add(new Object[]{slidingQuantity, slidingUnit});
+  return sw;
+}
+
+public FixedWindow and(long quantity, Quantification.Unit unit)
+{
+  size.add(new Object[]{quantity, unit});
+  return this;
+}
+
+public List<Object[]> getSize()
+{
+  return size;
+}
+  }
+
+  public static class SlidingWindow extends FixedWindow
--- End diff --

The FixedWindow can be treated as special case of SlidingWindow( slide step 
same as size ). If treat it in this way, we don't need to handle FixedWindow 
specifically


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #320: APEXMALHAR-2120 #resolve #comment solve probl...

2016-06-15 Thread brightchen

GitHub user brightchen opened a pull request:

https://github.com/apache/apex-malhar/pull/320

APEXMALHAR-2120 #resolve #comment solve problems of KafkaInputOperatoâ¦

â¦rTest and AbstractKafkaInputOperator

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2120

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/320.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #320


commit 7055fa2ddcd931b18e75bbb96b6e97f24f1f5889
Author: brightchen <bri...@datatorrent.com>
Date:   2016-06-14T23:30:17Z

APEXMALHAR-2120 #resolve #comment solve problems of KafkaInputOperatorTest 
and AbstractKafkaInputOperator




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #319: APEXMALHAR-2085: REVIEW ONLY: Operator suppor...

2016-06-24 Thread brightchen

Github user brightchen commented on a diff in the pull request:

https://github.com/apache/apex-malhar/pull/319#discussion_r68475212
  
--- Diff: 
library/src/main/java/org/apache/apex/malhar/lib/window/Window.java ---
@@ -0,0 +1,179 @@
+/**
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied.  See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+package org.apache.apex.malhar.lib.window;
+
+import java.util.Comparator;
+
+import org.apache.hadoop.classification.InterfaceStability;
+
+/**
+ * This interface describes the individual window.
+ */
+@InterfaceStability.Evolving
+public interface Window
--- End diff --

I think for Window, we could only provide one interface isWithinWIndow(long 
time); So for GlobalWindow, we can simplly return true. And in SessionWindow, 
instead of using static method to merge the window, we can just extendWindow().


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #320: APEXMALHAR-2120 #resolve #comment solve probl...

2016-06-15 Thread brightchen

GitHub user brightchen reopened a pull request:

https://github.com/apache/apex-malhar/pull/320

APEXMALHAR-2120 #resolve #comment solve problems of KafkaInputOperatoâ¦

â¦rTest and AbstractKafkaInputOperator

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2120

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/320.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #320


commit 6f99fb20da7214f493b442ce4ba3f447ec51cd13
Author: brightchen <bri...@datatorrent.com>
Date:   2016-06-14T23:30:17Z

APEXMALHAR-2120 #resolve #comment solve problems of KafkaInputOperatorTest 
and AbstractKafkaInputOperator




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #320: APEXMALHAR-2120 #resolve #comment solve probl...

2016-06-15 Thread brightchen

Github user brightchen closed the pull request at:

https://github.com/apache/apex-malhar/pull/320


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #294: APEXMALHAR-2076 #resolve #comment add Abstrac...

2016-07-21 Thread brightchen

Github user brightchen closed the pull request at:

https://github.com/apache/apex-malhar/pull/294


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #294: APEXMALHAR-2076 #resolve #comment add Abstrac...

2016-07-21 Thread brightchen

GitHub user brightchen reopened a pull request:

https://github.com/apache/apex-malhar/pull/294

APEXMALHAR-2076 #resolve #comment add AbstractTupleUniqueExactlyOnceKâ¦

â¦afkaOutputOperator

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2076

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/294.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #294


commit b45b6fdf66acdefe65a7fd0513e256460a5eb10f
Author: brightchen <bri...@datatorrent.com>
Date:   2016-05-25T20:01:26Z

APEXMALHAR-2076 #resolve #comment add 
AbstractTupleUniqueExactlyOnceKafkaOutputOperator




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #332: Kafka input test: just used for test Travis i...

2016-07-06 Thread brightchen

Github user brightchen closed the pull request at:

https://github.com/apache/apex-malhar/pull/332


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #321: APEXMALHAR-2120 #resolve #comment solve probl...

2016-06-20 Thread brightchen

Github user brightchen commented on a diff in the pull request:

https://github.com/apache/apex-malhar/pull/321#discussion_r67772302
  
--- Diff: kafka/pom.xml ---
@@ -198,7 +198,7 @@
 
   org.apache.kafka
   kafka_2.11
-  0.9.0.0
--- End diff --

0.9.0.1 fixed some bugs, it should be more stable than 0.9.0.0. I think 
it's better to upgrade before a lot of customers using it. Following is Kafka 
0.9.0.1 release notes: http://apache.claz.org/kafka/0.9.0.1/RELEASE_NOTES.html


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #370: APEXMALHAR-2182 #resolve #comment benchmark f...

2016-08-17 Thread brightchen

GitHub user brightchen reopened a pull request:

https://github.com/apache/apex-malhar/pull/370

APEXMALHAR-2182 #resolve #comment benchmark for spillable data structâ¦

â¦ure and storage

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2182

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/370.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #370


commit ea4f7a434ee97c1079bbf9432e9443cb203aa502
Author: brightchen <bri...@datatorrent.com>
Date:   2016-08-12T23:43:45Z

APEXMALHAR-2182 #resolve #comment benchmark for spillable data structure 
and storage




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-core pull request #455: APEXCORE-606-RV: review only: optimise kryo out...

2017-01-27 Thread brightchen

Github user brightchen closed the pull request at:

https://github.com/apache/apex-core/pull/455


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-core pull request #455: APEXCORE-606-RV: review only: optimise kryo out...

2017-01-26 Thread brightchen

GitHub user brightchen opened a pull request:

https://github.com/apache/apex-core/pull/455

APEXCORE-606-RV: review only: optimise kryo output stream.

This is a prototype of optimize kryo output stream. The main focus is 
avoiding memory copy and garbage collection to increase the performance.
- SerializationBuffer is the the class extends kryo Output which use the 
WindowedBlockStream to manage the memory.
- WindowedBlockStream is the memory management class which support manage 
memory blocks based windows. The windowed related function can be ignored now
- BlockStream is the super class of WindowedBlockStream which manage blocks
- CodecPerformanceTest is the class which test the performance. Please 
change the CodecPerformanceTest.loop to a number bigger than 100 before really 
do the performance test. And test the use case one by one as initialize impact 
the performance.
- PartitionSerde is the class serialize partition and object which can be 
used by BufferServerPublisher.
- BufferServerPublisher.put_new(Object) is the implementation use new 
stream.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-core APEXCORE-606-RV

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-core/pull/455.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #455


commit a540faa7f60fc220149cf087efee0ac3698ff2ce
Author: brightchen <bri...@datatorrent.com>
Date:   2016-12-27T23:09:11Z

APEXCORE-606-RV: review only: optimise kryo output stream.




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #518: APEXMALHAR-2359 #resolve #comment Optimise fi...

2017-01-17 Thread brightchen

GitHub user brightchen reopened a pull request:

https://github.com/apache/apex-malhar/pull/518

APEXMALHAR-2359 #resolve #comment Optimise fire trigger to avoid go tâ¦

â¦hrough all data

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2359

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/518.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #518


commit 511795d80f9b765f3c9573147ffe3f45b8283292
Author: brightchen <bri...@datatorrent.com>
Date:   2016-11-29T23:05:09Z

APEXMALHAR-2359 #resolve #comment Optimise fire trigger to avoid go through 
all data




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #518: APEXMALHAR-2359 #resolve #comment Optimise fi...

2017-01-17 Thread brightchen

Github user brightchen closed the pull request at:

https://github.com/apache/apex-malhar/pull/518


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #370: APEXMALHAR-2182 #resolve #comment benchmark f...

2016-08-15 Thread brightchen

GitHub user brightchen opened a pull request:

https://github.com/apache/apex-malhar/pull/370

APEXMALHAR-2182 #resolve #comment benchmark for spillable data structâ¦

â¦ure and storage

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2182

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/370.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #370


commit ea4f7a434ee97c1079bbf9432e9443cb203aa502
Author: brightchen <bri...@datatorrent.com>
Date:   2016-08-12T23:43:45Z

APEXMALHAR-2182 #resolve #comment benchmark for spillable data structure 
and storage




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #566: APEXMALHAR-2428 CompositeAccumulation for win...

2017-02-27 Thread brightchen

GitHub user brightchen opened a pull request:

https://github.com/apache/apex-malhar/pull/566

APEXMALHAR-2428 CompositeAccumulation for windowed operator



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2428

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/566.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #566


commit e2b1d31e5e69c0515db68baccf1fb97f8f7077c0
Author: brightchen <bri...@datatorrent.com>
Date:   2017-01-27T20:37:07Z

APEXMALHAR-2428 CompositeAccumulation for windowed operator




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #375: Apexmalhar-2190 shared memory for serialize -...

2016-09-06 Thread brightchen

Github user brightchen closed the pull request at:

https://github.com/apache/apex-malhar/pull/375


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #398: APEXMALHAR-2205 #resolve #comment State manag...

2016-09-01 Thread brightchen

GitHub user brightchen opened a pull request:

https://github.com/apache/apex-malhar/pull/398

APEXMALHAR-2205 #resolve #comment State management benchmark

previous PR closed by accident. 
https://github.com/apache/apex-malhar/pull/386

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2205

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/398.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #398


commit c5a12e4e747c5be840a16e4c932cbc1dbff79894
Author: brightchen <bri...@datatorrent.com>
Date:   2016-08-26T23:09:12Z

APEXMALHAR-2205 #resolve #comment State management benchmark




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #386: APEXMALHAR-2205 State management benchmark

2016-09-01 Thread brightchen

Github user brightchen closed the pull request at:

https://github.com/apache/apex-malhar/pull/386


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #404: APEXMALHAR-2190 #resolve #comment Use reusabl...

2016-09-07 Thread brightchen

GitHub user brightchen opened a pull request:

https://github.com/apache/apex-malhar/pull/404

APEXMALHAR-2190 #resolve #comment Use reusable buffer to serial spillâ¦

â¦able data structure

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2190-PR

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/404.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #404


commit 7bddb85553f7a870473a7a3dbc9ac35fb8511b95
Author: brightchen <bri...@datatorrent.com>
Date:   2016-08-16T00:46:27Z

APEXMALHAR-2190 #resolve #comment Use reusable buffer to serial spillable 
data structure




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #386: APEXMALHAR-2205 State management benchmark

2016-08-29 Thread brightchen

Github user brightchen closed the pull request at:

https://github.com/apache/apex-malhar/pull/386


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #386: APEXMALHAR-2205 State management benchmark

2016-08-29 Thread brightchen

GitHub user brightchen reopened a pull request:

https://github.com/apache/apex-malhar/pull/386

APEXMALHAR-2205 State management benchmark



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2205

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/386.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #386


commit eea3d04910e4b06983cacb98a1e0d1429d0f968d
Author: brightchen <bri...@datatorrent.com>
Date:   2016-08-26T23:09:12Z

APEXMALHAR-2205 State management benchmark




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #412: APEXMALHAR-2205 #resolve #comment State manag...

2016-09-14 Thread brightchen

Github user brightchen closed the pull request at:

https://github.com/apache/apex-malhar/pull/412


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #404: APEXMALHAR-2190 #resolve #comment Use reusabl...

2016-09-26 Thread brightchen

Github user brightchen closed the pull request at:

https://github.com/apache/apex-malhar/pull/404


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #404: APEXMALHAR-2190 #resolve #comment Use reusabl...

2016-09-26 Thread brightchen

GitHub user brightchen reopened a pull request:

https://github.com/apache/apex-malhar/pull/404

APEXMALHAR-2190 #resolve #comment Use reusable buffer to serial spillâ¦

â¦able data structure

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2190-PR

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/404.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #404


commit 13e8b60811501f8bdbb75b4112c9a74676ec3b3c
Author: brightchen <bri...@datatorrent.com>
Date:   2016-08-16T00:46:27Z

APEXMALHAR-2190 #resolve #comment Use reusable buffer to serial spillable 
data structure




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #404: APEXMALHAR-2190 #resolve #comment Use reusabl...

2016-09-29 Thread brightchen

GitHub user brightchen reopened a pull request:

https://github.com/apache/apex-malhar/pull/404

APEXMALHAR-2190 #resolve #comment Use reusable buffer to serial spillâ¦

â¦able data structure

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2190-PR

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/404.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #404


commit 109a339981942494fa9ea9c7eb2fb7013167b512
Author: brightchen <bri...@datatorrent.com>
Date:   2016-08-16T00:46:27Z

APEXMALHAR-2190 #resolve #comment Use reusable buffer to serial spillable 
data structure




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #404: APEXMALHAR-2190 #resolve #comment Use reusabl...

2016-09-29 Thread brightchen

Github user brightchen closed the pull request at:

https://github.com/apache/apex-malhar/pull/404


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #415: APEXMALHAR-2243 #resolve #comment change name...

2016-09-19 Thread brightchen

GitHub user brightchen opened a pull request:

https://github.com/apache/apex-malhar/pull/415

APEXMALHAR-2243 #resolve #comment change name StoreOperator.setExeModâ¦

â¦eStr(String) to setExecModeStr

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2243

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/415.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #415


commit 0c4b3fce2a8f73dae18d7570ca54d76cf9098e5b
Author: brightchen <bri...@datatorrent.com>
Date:   2016-09-19T16:17:31Z

APEXMALHAR-2243 #resolve #comment change name 
StoreOperator.setExeModeStr(String) to setExecModeStr




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #404: APEXMALHAR-2190 #resolve #comment Use reusabl...

2016-09-21 Thread brightchen

Github user brightchen closed the pull request at:

https://github.com/apache/apex-malhar/pull/404


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #404: APEXMALHAR-2190 #resolve #comment Use reusabl...

2016-09-21 Thread brightchen

GitHub user brightchen reopened a pull request:

https://github.com/apache/apex-malhar/pull/404

APEXMALHAR-2190 #resolve #comment Use reusable buffer to serial spillâ¦

â¦able data structure

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2190-PR

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/404.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #404


commit 3541026395f2d13bc128dd7524eef7753fdd5dc6
Author: brightchen <bri...@datatorrent.com>
Date:   2016-08-16T00:46:27Z

APEXMALHAR-2190 #resolve #comment Use reusable buffer to serial spillable 
data structure




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #404: APEXMALHAR-2190 #resolve #comment Use reusabl...

2016-09-22 Thread brightchen

GitHub user brightchen reopened a pull request:

https://github.com/apache/apex-malhar/pull/404

APEXMALHAR-2190 #resolve #comment Use reusable buffer to serial spillâ¦

â¦able data structure

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2190-PR

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/404.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #404


commit b17ca37cf7f0ae8037ce69206e9ae914f8168d33
Author: brightchen <bri...@datatorrent.com>
Date:   2016-08-16T00:46:27Z

APEXMALHAR-2190 #resolve #comment Use reusable buffer to serial spillable 
data structure




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #370: APEXMALHAR-2182 #resolve #comment benchmark f...

2016-08-18 Thread brightchen

Github user brightchen closed the pull request at:

https://github.com/apache/apex-malhar/pull/370


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #375: Apexmalhar-2190 shared memory for serialize -...

2016-08-18 Thread brightchen

GitHub user brightchen opened a pull request:

https://github.com/apache/apex-malhar/pull/375

Apexmalhar-2190 shared memory for serialize - review only



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2190

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/375.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #375


commit 657669fdd35e99762c9009c037aae10c9849bc99
Author: brightchen <bri...@datatorrent.com>
Date:   2016-08-16T00:46:27Z

APEXMALHAR-2190 #resolve #comment Use shared memory to serial spillable 
data structure

commit 8b9529d34855fef6aa83408e40704df72f37a38e
Author: brightchen <bri...@datatorrent.com>
Date:   2016-08-17T19:06:04Z

APEXMALHAR-2190 #resolve #comment Use shared memory to serial spillable 
data structure




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #386: APEXMALHAR-2205 State management benchmark

2016-08-26 Thread brightchen

GitHub user brightchen opened a pull request:

https://github.com/apache/apex-malhar/pull/386

APEXMALHAR-2205 State management benchmark



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2205

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/386.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #386


commit 7be771bc5f58322fd8ddaf6f8caa8bc799791f9a
Author: brightchen <bri...@datatorrent.com>
Date:   2016-08-26T23:09:12Z

APEXMALHAR-2205 State management benchmark




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #386: APEXMALHAR-2205 State management benchmark

2016-08-29 Thread brightchen

Github user brightchen closed the pull request at:

https://github.com/apache/apex-malhar/pull/386


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #386: APEXMALHAR-2205 State management benchmark

2016-08-29 Thread brightchen

GitHub user brightchen reopened a pull request:

https://github.com/apache/apex-malhar/pull/386

APEXMALHAR-2205 State management benchmark



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2205

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/386.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #386


commit 7be771bc5f58322fd8ddaf6f8caa8bc799791f9a
Author: brightchen <bri...@datatorrent.com>
Date:   2016-08-26T23:09:12Z

APEXMALHAR-2205 State management benchmark




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #404: APEXMALHAR-2190 #resolve #comment Use reusabl...

2016-09-27 Thread brightchen

GitHub user brightchen reopened a pull request:

https://github.com/apache/apex-malhar/pull/404

APEXMALHAR-2190 #resolve #comment Use reusable buffer to serial spillâ¦

â¦able data structure

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2190-PR

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/404.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #404


commit 598943fd5474be08437430c643987b4d0894c553
Author: brightchen <bri...@datatorrent.com>
Date:   2016-08-16T00:46:27Z

APEXMALHAR-2190 #resolve #comment Use reusable buffer to serial spillable 
data structure




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #404: APEXMALHAR-2190 #resolve #comment Use reusabl...

2016-09-27 Thread brightchen

Github user brightchen closed the pull request at:

https://github.com/apache/apex-malhar/pull/404


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #404: APEXMALHAR-2190 #resolve #comment Use reusabl...

2016-10-10 Thread brightchen

Github user brightchen closed the pull request at:

https://github.com/apache/apex-malhar/pull/404


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #404: APEXMALHAR-2190 #resolve #comment Use reusabl...

2016-10-10 Thread brightchen

GitHub user brightchen reopened a pull request:

https://github.com/apache/apex-malhar/pull/404

APEXMALHAR-2190 #resolve #comment Use reusable buffer to serial spillâ¦

â¦able data structure

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2190-PR

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/404.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #404


commit 35b54993d7b5003833e4584feef2d102756b4bc2
Author: brightchen <bri...@datatorrent.com>
Date:   2016-08-16T00:46:27Z

APEXMALHAR-2190 #resolve #comment Use reusable buffer to serial spillable 
data structure




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #470: APEXMALHAR-2317 #resolve #comment Change Spil...

2016-10-26 Thread brightchen

GitHub user brightchen opened a pull request:

https://github.com/apache/apex-malhar/pull/470

APEXMALHAR-2317 #resolve #comment Change SpillableBenchmarkApp to adaâ¦

â¦pt the change on Spillable Data Structure

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2317

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/470.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #470


commit d8b5fe7bdcbb3cbdaa7a1ddda822ead3f3fbb7af
Author: brightchen <bri...@datatorrent.com>
Date:   2016-10-26T18:28:34Z

APEXMALHAR-2317 #resolve #comment Change SpillableBenchmarkApp to adapt the 
change on Spillable Data Structure




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #481: APEXMALHAR-2321 #resolve #comment Improve Buc...

2016-11-07 Thread brightchen

Github user brightchen closed the pull request at:

https://github.com/apache/apex-malhar/pull/481


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #488: APEXMALHAR-2331 #resolve #comment StateTracke...

2016-11-08 Thread brightchen

GitHub user brightchen opened a pull request:

https://github.com/apache/apex-malhar/pull/488

APEXMALHAR-2331 #resolve #comment StateTracker#bucketAccessed should â¦

â¦add bucket to bucketAccessTimes

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2331

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/488.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #488


commit b1c829afb46fc6d505c58a4938901061e3fb38fc
Author: brightchen <bri...@datatorrent.com>
Date:   2016-11-08T18:53:43Z

APEXMALHAR-2331 #resolve #comment StateTracker#bucketAccessed should add 
bucket to bucketAccessTimes




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #491: review only: Apexmalhar 2335

2016-11-10 Thread brightchen

Github user brightchen closed the pull request at:

https://github.com/apache/apex-malhar/pull/491


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #491: review only: Apexmalhar 2335

2016-11-10 Thread brightchen

GitHub user brightchen opened a pull request:

https://github.com/apache/apex-malhar/pull/491

review only: Apexmalhar 2335

please ignore test log information and monitor related code

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2335

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/491.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #491


commit a07b905c782524e104663e6bd1c3b02c4c686cc7
Author: brightchen <bri...@datatorrent.com>
Date:   2016-11-10T18:52:38Z

APEXMALHAR-2335 #resolve #comment Problems on StateTracker#bucketAccessed

commit cdd1194af863154d88a752bde256c0c57c746cd8
Author: brightchen <bri...@datatorrent.com>
Date:   2016-11-10T18:52:48Z

Merge branch 'master' of github.com:apache/apex-malhar into APEXMALHAR-2335

commit 4edb5b2f968c116239a666206cc4d1056a3326c6
Author: brightchen <bri...@datatorrent.com>
Date:   2016-11-10T22:13:44Z

add monitor and debug information etc

commit 3acc685c8c16f01201f4de2198f3e0af14e3180e
Author: brightchen <bri...@datatorrent.com>
Date:   2016-11-10T22:14:00Z

add monitor and debug information etc




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #473: APEXMALHAR-2289 #resolve #comment Add resourc...

2016-11-04 Thread brightchen

Github user brightchen closed the pull request at:

https://github.com/apache/apex-malhar/pull/473


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #404: APEXMALHAR-2190 #resolve #comment Use reusabl...

2016-10-18 Thread brightchen

GitHub user brightchen reopened a pull request:

https://github.com/apache/apex-malhar/pull/404

APEXMALHAR-2190 #resolve #comment Use reusable buffer to serial spillâ¦

â¦able data structure

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2190-PR

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/404.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #404


commit 66d8defb767ced52c6563c9710a832395269625e
Author: brightchen <bri...@datatorrent.com>
Date:   2016-08-16T00:46:27Z

APEXMALHAR-2190 #resolve #comment Use reusable buffer to serial spillable 
data structure




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #404: APEXMALHAR-2190 #resolve #comment Use reusabl...

2016-10-18 Thread brightchen

Github user brightchen closed the pull request at:

https://github.com/apache/apex-malhar/pull/404


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #404: APEXMALHAR-2190 #resolve #comment Use reusabl...

2016-10-18 Thread brightchen

Github user brightchen closed the pull request at:

https://github.com/apache/apex-malhar/pull/404


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #404: APEXMALHAR-2190 #resolve #comment Use reusabl...

2016-10-18 Thread brightchen

GitHub user brightchen reopened a pull request:

https://github.com/apache/apex-malhar/pull/404

APEXMALHAR-2190 #resolve #comment Use reusable buffer to serial spillâ¦

â¦able data structure

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2190-PR

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/404.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #404


commit 5e5e968086a774ab8067ae7e6d29e31f3b68af54
Author: brightchen <bri...@datatorrent.com>
Date:   2016-08-16T00:46:27Z

APEXMALHAR-2190 #resolve #comment Use reusable buffer to serial spillable 
data structure




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #493: APEXMALHAR-2335 APEXMALHAR-2333 APEXMALHAR-23...

2016-11-11 Thread brightchen

Github user brightchen closed the pull request at:

https://github.com/apache/apex-malhar/pull/493


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #493: APEXMALHAR-2335 APEXMALHAR-2333 APEXMALHAR-23...

2016-11-11 Thread brightchen

GitHub user brightchen reopened a pull request:

https://github.com/apache/apex-malhar/pull/493

APEXMALHAR-2335 APEXMALHAR-2333 APEXMALHAR-2334 #resolve #comment Proâ¦

â¦blems on StateTracker

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2335-PR

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/493.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #493


commit b7ca8ea5fd5a17e3be70c3117aec057776eb995c
Author: brightchen <bri...@datatorrent.com>
Date:   2016-11-10T22:59:52Z

APEXMALHAR-2335 APEXMALHAR-2333 APEXMALHAR-2334 #resolve #comment Problems 
on StateTracker




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #514: APEXMALHAR-2358 #resolve #comment Optimise Ge...

2016-11-28 Thread brightchen

GitHub user brightchen opened a pull request:

https://github.com/apache/apex-malhar/pull/514

APEXMALHAR-2358 #resolve #comment Optimise GenericSerde to use specifâ¦

â¦ic serde to improve the performance

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2358

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/514.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #514


commit 64167a44afd4b2a36e91633ee6a2fd28d1d24792
Author: brightchen <bri...@datatorrent.com>
Date:   2016-11-28T19:17:14Z

APEXMALHAR-2358 #resolve #comment Optimise GenericSerde to use specific 
serde to improve the performance




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #515: APEXMALHAR-2350 #resolve #comment The key and...

2016-11-28 Thread brightchen

GitHub user brightchen opened a pull request:

https://github.com/apache/apex-malhar/pull/515

APEXMALHAR-2350 #resolve #comment The key and value stream should matâ¦

â¦ch with the bucket

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2350

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/515.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #515


commit 5eac254cf8cad3dd928743835d70b62fba535fbc
Author: brightchen <bri...@datatorrent.com>
Date:   2016-11-29T00:17:15Z

APEXMALHAR-2350 #resolve #comment The key and value stream should match 
with the bucket




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #499: APEXMALHAR-2343 #resolve #comment Count Accum...

2016-11-16 Thread brightchen

GitHub user brightchen opened a pull request:

https://github.com/apache/apex-malhar/pull/499

APEXMALHAR-2343 #resolve #comment Count Accumulation should only incrâ¦

â¦ease one for each tuple

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2343

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/499.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #499


commit 0f2d0e8d0df9db6361b7037c735030879392be61
Author: brightchen <bri...@datatorrent.com>
Date:   2016-11-16T19:29:46Z

APEXMALHAR-2343 #resolve #comment Count Accumulation should only increase 
one for each tuple




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #500: APEXMALHAR-2343 #resolve #comment Count Accum...

2016-11-16 Thread brightchen

GitHub user brightchen opened a pull request:

https://github.com/apache/apex-malhar/pull/500

APEXMALHAR-2343 #resolve #comment Count Accumulation should only incrâ¦

â¦ease one for each tuple

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2343

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/500.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #500






---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #499: APEXMALHAR-2343 #resolve #comment Count Accum...

2016-11-16 Thread brightchen

Github user brightchen closed the pull request at:

https://github.com/apache/apex-malhar/pull/499


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #488: APEXMALHAR-2331 #resolve #comment StateTracke...

2016-11-16 Thread brightchen

Github user brightchen closed the pull request at:

https://github.com/apache/apex-malhar/pull/488


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #294: APEXMALHAR-2076 #resolve #comment add Abstrac...

2016-11-16 Thread brightchen

Github user brightchen closed the pull request at:

https://github.com/apache/apex-malhar/pull/294


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #502: review only: Windowed Operator benchmark

2016-11-17 Thread brightchen

GitHub user brightchen opened a pull request:

https://github.com/apache/apex-malhar/pull/502

review only: Windowed Operator benchmark



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2339

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/502.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #502


commit 32e73b7f45c9ea5132163826a56a32f7ebf7d7cf
Author: brightchen <bri...@datatorrent.com>
Date:   2016-11-16T19:25:26Z

APEXMALHAR-2339 doing

commit 2405d18f7e822c754f92446d9fc52c0aed0747fb
Author: brightchen <bri...@datatorrent.com>
Date:   2016-11-16T21:46:07Z

APEXMALHAR-2339 initial version

commit ffb370e693508221e948db10cececd5b636d14f8
Author: brightchen <bri...@datatorrent.com>
Date:   2016-11-17T21:55:27Z

APEXMALHAR-2339 initial version




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #493: APEXMALHAR-2335 APEXMALHAR-2333 APEXMALHAR-23...

2016-11-13 Thread brightchen

GitHub user brightchen reopened a pull request:

https://github.com/apache/apex-malhar/pull/493

APEXMALHAR-2335 APEXMALHAR-2333 APEXMALHAR-2334 #resolve #comment Proâ¦

â¦blems on StateTracker

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2335-PR

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/493.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #493


commit 391bad220aaef0ee54d698064d5a9218a52d98fa
Author: brightchen <bri...@datatorrent.com>
Date:   2016-11-10T22:59:52Z

APEXMALHAR-2335 APEXMALHAR-2333 APEXMALHAR-2334 #resolve #comment Problems 
on StateTracker




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #493: APEXMALHAR-2335 APEXMALHAR-2333 APEXMALHAR-23...

2016-11-13 Thread brightchen

Github user brightchen closed the pull request at:

https://github.com/apache/apex-malhar/pull/493


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #477: APEXMALHAR-2320 #resolve #comment use Seriali...

2016-10-31 Thread brightchen

GitHub user brightchen opened a pull request:

https://github.com/apache/apex-malhar/pull/477

APEXMALHAR-2320 #resolve #comment use SerializationBuffer implement Fâ¦

â¦SWindowDataManager.toSlice()

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2320

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/477.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #477


commit 11c8c222a21d0533c582eb5a133cc2620050c094
Author: brightchen <bri...@datatorrent.com>
Date:   2016-10-31T23:50:07Z

APEXMALHAR-2320 #resolve #comment use SerializationBuffer implement 
FSWindowDataManager.toSlice()




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #481: APEXMALHAR-2321 #resolve #comment Improve Buc...

2016-11-03 Thread brightchen

Github user brightchen closed the pull request at:

https://github.com/apache/apex-malhar/pull/481


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #481: APEXMALHAR-2321 #resolve #comment Improve Buc...

2016-11-03 Thread brightchen

GitHub user brightchen reopened a pull request:

https://github.com/apache/apex-malhar/pull/481

APEXMALHAR-2321 #resolve #comment Improve Buckets memory management



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2321

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/481.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #481


commit d16ce8b5f6364a3562a9e5c94dfb7763597ca8a0
Author: brightchen <bri...@datatorrent.com>
Date:   2016-11-01T21:30:55Z

APEXMALHAR-2321 #resolve #comment Improve Buckets memory management




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #477: APEXMALHAR-2320 #resolve #comment use Seriali...

2016-11-03 Thread brightchen

Github user brightchen closed the pull request at:

https://github.com/apache/apex-malhar/pull/477


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #477: APEXMALHAR-2320 #resolve #comment use Seriali...

2016-11-03 Thread brightchen

GitHub user brightchen reopened a pull request:

https://github.com/apache/apex-malhar/pull/477

APEXMALHAR-2320 #resolve #comment use SerializationBuffer implement Fâ¦

â¦SWindowDataManager.toSlice()

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2320

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/477.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #477


commit dfcd2d5678b62ac383173f4780e6604c6a0cfd62
Author: brightchen <bri...@datatorrent.com>
Date:   2016-10-31T23:50:07Z

APEXMALHAR-2320 #resolve #comment use SerializationBuffer implement 
FSWindowDataManager.toSlice()




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #482: APEXMALHAR-2327 #resolve #comment BucketsFile...

2016-11-03 Thread brightchen

GitHub user brightchen opened a pull request:

https://github.com/apache/apex-malhar/pull/482

APEXMALHAR-2327 #resolve #comment BucketsFileSystem.writeBucketData()â¦

â¦ call Slice.toByteArray() cause allocate unnecessary memory

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2327

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/482.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #482


commit ed931fd49ae3c7c9d3a17a0ca9bd7e492c914bc2
Author: brightchen <bri...@datatorrent.com>
Date:   2016-11-03T22:38:16Z

APEXMALHAR-2327 #resolve #comment BucketsFileSystem.writeBucketData() call 
Slice.toByteArray() cause allocate unnecessary memory




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #473: APEXMALHAR-2289 #resolve #comment Add resourc...

2016-10-28 Thread brightchen

GitHub user brightchen opened a pull request:

https://github.com/apache/apex-malhar/pull/473

APEXMALHAR-2289 #resolve #comment Add resource monitor



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2289-PR

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/473.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #473


commit 861be1930cb0c282e14baf208ab5e9fbeb8878cf
Author: brightchen <bri...@datatorrent.com>
Date:   2016-10-28T23:19:15Z

APEXMALHAR-2289 #resolve #comment Add resource monitor




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #481: APEXMALHAR-2321 #resolve #comment Improve Buc...

2016-11-02 Thread brightchen

GitHub user brightchen opened a pull request:

https://github.com/apache/apex-malhar/pull/481

APEXMALHAR-2321 #resolve #comment Improve Buckets memory management



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2321

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/481.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #481


commit d16ce8b5f6364a3562a9e5c94dfb7763597ca8a0
Author: brightchen <bri...@datatorrent.com>
Date:   2016-11-01T21:30:55Z

APEXMALHAR-2321 #resolve #comment Improve Buckets memory management




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #404: APEXMALHAR-2190 #resolve #comment Use reusabl...

2016-10-11 Thread brightchen

GitHub user brightchen reopened a pull request:

https://github.com/apache/apex-malhar/pull/404

APEXMALHAR-2190 #resolve #comment Use reusable buffer to serial spillâ¦

â¦able data structure

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2190-PR

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/404.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #404


commit 5c3f8fd54fc5b649b5bb8bb91765c1d61e0f8d92
Author: brightchen <bri...@datatorrent.com>
Date:   2016-08-16T00:46:27Z

APEXMALHAR-2190 #resolve #comment Use reusable buffer to serial spillable 
data structure




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #404: APEXMALHAR-2190 #resolve #comment Use reusabl...

2016-10-11 Thread brightchen

Github user brightchen closed the pull request at:

https://github.com/apache/apex-malhar/pull/404


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #404: APEXMALHAR-2190 #resolve #comment Use reusabl...

2016-10-14 Thread brightchen

Github user brightchen closed the pull request at:

https://github.com/apache/apex-malhar/pull/404


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #404: APEXMALHAR-2190 #resolve #comment Use reusabl...

2016-10-11 Thread brightchen

Github user brightchen closed the pull request at:

https://github.com/apache/apex-malhar/pull/404


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #404: APEXMALHAR-2190 #resolve #comment Use reusabl...

2016-10-11 Thread brightchen

GitHub user brightchen reopened a pull request:

https://github.com/apache/apex-malhar/pull/404

APEXMALHAR-2190 #resolve #comment Use reusable buffer to serial spillâ¦

â¦able data structure

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2190-PR

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/404.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #404


commit 5c3f8fd54fc5b649b5bb8bb91765c1d61e0f8d92
Author: brightchen <bri...@datatorrent.com>
Date:   2016-08-16T00:46:27Z

APEXMALHAR-2190 #resolve #comment Use reusable buffer to serial spillable 
data structure




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #521: APEXMALHAR-2366 #resolve #comment Apply Bloom...

2016-12-08 Thread brightchen

GitHub user brightchen opened a pull request:

https://github.com/apache/apex-malhar/pull/521

APEXMALHAR-2366 #resolve #comment Apply BloomFilter to Bucket, use inâ¦

â¦ternal BloomFilter

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2366

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/521.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #521


commit 08ab2d4ae45c28245a7752a9ecd28d178d232e7b
Author: brightchen <bri...@datatorrent.com>
Date:   2016-12-05T19:34:48Z

APEXMALHAR-2366 #resolve #comment Apply BloomFilter to Bucket, use internal 
BloomFilter




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #518: APEXMALHAR-2359 #resolve #comment Optimise fi...

2017-01-13 Thread brightchen

Github user brightchen closed the pull request at:

https://github.com/apache/apex-malhar/pull/518


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #518: APEXMALHAR-2359 #resolve #comment Optimise fi...

2017-01-13 Thread brightchen

GitHub user brightchen reopened a pull request:

https://github.com/apache/apex-malhar/pull/518

APEXMALHAR-2359 #resolve #comment Optimise fire trigger to avoid go tâ¦

â¦hrough all data

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2359

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/518.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #518


commit 5cea599d5a7965b3771c840d6399790c2ad8
Author: brightchen <bri...@datatorrent.com>
Date:   2016-11-29T23:05:09Z

APEXMALHAR-2359 #resolve #comment Optimise fire trigger to avoid go through 
all data




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #518: APEXMALHAR-2359 #resolve #comment Optimise fi...

2016-11-30 Thread brightchen

GitHub user brightchen opened a pull request:

https://github.com/apache/apex-malhar/pull/518

APEXMALHAR-2359 #resolve #comment Optimise fire trigger to avoid go tâ¦

â¦hrough all data

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2359

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/518.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #518


commit 665452248dfd437c176e5364665266839943c30b
Author: brightchen <bri...@datatorrent.com>
Date:   2016-11-29T23:05:09Z

APEXMALHAR-2359 #resolve #comment Optimise fire trigger to avoid go through 
all data




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #500: APEXMALHAR-2343 #resolve #comment Count Accum...

2017-01-03 Thread brightchen

Github user brightchen closed the pull request at:

https://github.com/apache/apex-malhar/pull/500


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #514: APEXMALHAR-2358 #resolve #comment Optimise Ge...

2017-01-02 Thread brightchen

GitHub user brightchen reopened a pull request:

https://github.com/apache/apex-malhar/pull/514

APEXMALHAR-2358 #resolve #comment Optimise GenericSerde to use specifâ¦

â¦ic serde to improve the performance

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2358

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/514.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #514


commit 96835c503060f35ec3e8bb7340554f6c27d303f4
Author: brightchen <bri...@datatorrent.com>
Date:   2016-11-28T19:17:14Z

APEXMALHAR-2358 #resolve #comment Optimise GenericSerde to use specific 
serde to improve the performance




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #514: APEXMALHAR-2358 #resolve #comment Optimise Ge...

2017-01-02 Thread brightchen

Github user brightchen closed the pull request at:

https://github.com/apache/apex-malhar/pull/514


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #574: APEXMALHAR-2435 #resolve #comment specify Key...

2017-03-08 Thread brightchen

GitHub user brightchen reopened a pull request:

https://github.com/apache/apex-malhar/pull/574

APEXMALHAR-2435 #resolve #comment specify KeyedWindowedOperatorBenchmâ¦

â¦arkApp application name

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2435

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/574.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #574


commit e4dbb84910ad846f3b09ab221f87eb2150294d26
Author: brightchen <bri...@datatorrent.com>
Date:   2017-03-08T00:40:27Z

APEXMALHAR-2435 #resolve #comment specify KeyedWindowedOperatorBenchmarkApp 
application name




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-malhar pull request #573: APEXMALHAR-2433 #resolve #comment Add readme ...

2017-03-06 Thread brightchen

GitHub user brightchen opened a pull request:

https://github.com/apache/apex-malhar/pull/573

APEXMALHAR-2433 #resolve #comment Add readme for Windowing Benchmark



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2433

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/573.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #573


commit 097869da4ced6d8eab14bc4b28e0024cc5df1746
Author: brightchen <bri...@datatorrent.com>
Date:   2017-03-06T21:33:51Z

APEXMALHAR-2433 #resolve #comment Add readme for Windowing Benchmark




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

89 matches

Mail list logo