[jira] [Comment Edited] (APEXCORE-592) Returning description field in defaultProperties during apex cli call get-app-package-info

[Sandesh (JIRA)]

[ 
https://issues.apache.org/jira/browse/APEXCORE-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15855014#comment-15855014
 ] 

Sandesh edited comment on APEXCORE-592 at 2/7/17 12:15 AM:
---

Have you looked at get-jar-operator-properties & get-jar-operator-classes 
commands in the CLI? They use OperatorDiscoverer (TypeGraph), which reads from 
the JavaDoc. It is better to explore that option.


was (Author: sandesh):
Have you looked at get-jar-operator-properties & get-jar-operator-classes 
commands in the CLI? They use OperatorDiscoverer and internally TypeGraph, 
which reads from the JavaDoc. 

> Returning description field in defaultProperties during apex cli call 
> get-app-package-info
> --
>
> Key: APEXCORE-592
> URL: https://issues.apache.org/jira/browse/APEXCORE-592
> Project: Apache Apex Core
>  Issue Type: Improvement
>Reporter: Ajay Gupta
>Assignee: Ajay Gupta
>Priority: Minor
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Currently for an operator property, only the value field is returned. The 
> operator property can have a description describing the property. This task 
> is created to return this filed for that operator property.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (APEXCORE-592) Returning description field in defaultProperties during apex cli call get-app-package-info

[Sandesh (JIRA)]

[ 
https://issues.apache.org/jira/browse/APEXCORE-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15855014#comment-15855014
 ] 

Sandesh edited comment on APEXCORE-592 at 2/7/17 12:14 AM:
---

Have you looked at get-jar-operator-properties & get-jar-operator-classes 
commands in the CLI? They use OperatorDiscoverer and internally TypeGraph, 
which reads from the JavaDoc. 


was (Author: sandesh):
Have you looked at get-jar-operator-properties & get-jar-operator-classes 
commands in the CLI? They OperatorDiscoverer and internally TypeGraph, which 
reads from the JavaDoc. 

> Returning description field in defaultProperties during apex cli call 
> get-app-package-info
> --
>
> Key: APEXCORE-592
> URL: https://issues.apache.org/jira/browse/APEXCORE-592
> Project: Apache Apex Core
>  Issue Type: Improvement
>Reporter: Ajay Gupta
>Assignee: Ajay Gupta
>Priority: Minor
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Currently for an operator property, only the value field is returned. The 
> operator property can have a description describing the property. This task 
> is created to return this filed for that operator property.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (APEXCORE-592) Returning description field in defaultProperties during apex cli call get-app-package-info

[Sandesh (JIRA)]

[ 
https://issues.apache.org/jira/browse/APEXCORE-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15855014#comment-15855014
 ] 

Sandesh commented on APEXCORE-592:
--

Have you looked at get-jar-operator-properties & get-jar-operator-classes 
commands in the CLI? They OperatorDiscoverer and internally TypeGraph, which 
reads from the JavaDoc. 

> Returning description field in defaultProperties during apex cli call 
> get-app-package-info
> --
>
> Key: APEXCORE-592
> URL: https://issues.apache.org/jira/browse/APEXCORE-592
> Project: Apache Apex Core
>  Issue Type: Improvement
>Reporter: Ajay Gupta
>Assignee: Ajay Gupta
>Priority: Minor
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Currently for an operator property, only the value field is returned. The 
> operator property can have a description describing the property. This task 
> is created to return this filed for that operator property.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (APEXCORE-592) Returning description field in defaultProperties during apex cli call get-app-package-info

[Sandesh (JIRA)]

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

Sandesh reassigned APEXCORE-592:


Assignee: Ajay Gupta

> Returning description field in defaultProperties during apex cli call 
> get-app-package-info
> --
>
> Key: APEXCORE-592
> URL: https://issues.apache.org/jira/browse/APEXCORE-592
> Project: Apache Apex Core
>  Issue Type: Improvement
>Reporter: Ajay Gupta
>Assignee: Ajay Gupta
>Priority: Minor
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Currently for an operator property, only the value field is returned. The 
> operator property can have a description describing the property. This task 
> is created to return this filed for that operator property.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (APEXCORE-640) BufferServer - purge crashes when the window purged is the last available

[Sandesh (JIRA)]

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

Sandesh updated APEXCORE-640:
-
Summary: BufferServer - purge crashes when the window purged is the last 
available  (was: BufferServer purge crashes when the window purged is the last 
available)

> BufferServer - purge crashes when the window purged is the last available
> -
>
> Key: APEXCORE-640
> URL: https://issues.apache.org/jira/browse/APEXCORE-640
> Project: Apache Apex Core
>  Issue Type: Bug
>Reporter: Sandesh
>Assignee: Sandesh
>
> While working on the unit test of BufferServer saw this behavior, 
> purge on the last window in the buffer server crashes it.
> java.lang.IllegalArgumentException: Invalid slice: offset=2118, length=0 
> array.length=4096
>   at com.datatorrent.netlet.util.Slice.(Slice.java:43)
>   at 
> com.datatorrent.bufferserver.util.SerializedData.(SerializedData.java:40)
>   at 
> com.datatorrent.bufferserver.internal.DataList$Block.purge(DataList.java:712)
>   at 
> com.datatorrent.bufferserver.internal.DataList.purge(DataList.java:192)
>   at 
> com.datatorrent.bufferserver.server.Server.handlePurgeRequest(Server.java:199)
>   at 
> com.datatorrent.bufferserver.server.Server.access$1100(Server.java:65)
>   at 
> com.datatorrent.bufferserver.server.Server$UnidentifiedClient.onMessage(Server.java:526)
>   at 
> com.datatorrent.netlet.AbstractLengthPrependerClient.read(AbstractLengthPrependerClient.java:149)
>   at com.datatorrent.netlet.AbstractClient.read(AbstractClient.java:104)
>   at 
> com.datatorrent.netlet.DefaultEventLoop.handleSelectedKey(DefaultEventLoop.java:364)
>   at 
> com.datatorrent.netlet.OptimizedEventLoop$SelectedSelectionKeySet.forEach(OptimizedEventLoop.java:59)
>   at 
> com.datatorrent.netlet.OptimizedEventLoop.runEventLoop(OptimizedEventLoop.java:192)
>   at 
> com.datatorrent.netlet.OptimizedEventLoop.runEventLoop(OptimizedEventLoop.java:157)
>   at 
> com.datatorrent.netlet.DefaultEventLoop.run(DefaultEventLoop.java:156)
>   at java.lang.Thread.run(Thread.java:745)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Setting JAVA Serializer to be used at App Level.

[Vlad Rozov]

Kryo allows to delegate serialization to Java. Add 
"@DefaultSerializer(JavaSerializer.class)" to a tuple class definition. 
As Santosh already mentioned, using Java serializer is not recommended 
as it affect performance.


I would recommend in the future to post similar questions on the 
user@apex. dev@apex is used to discuss development of the platform and 
the library.


Thank you,

Vlad

/Join us at Apex Big Data World-San Jose 
, April 4, 2017/
http://www.apexbigdata.com/san-jose-register.html 


On 2/5/17 22:34, Ambarish Pande wrote:

This is exactly what i wanted.
Thank You.

On Mon, Feb 6, 2017 at 11:35 AM, Hitesh Kapoor 
wrote:


Hi Ambarish,

Yes you can plug in your own serializer. You will have to set the
"STREAM_CODEC" port attribute to achieve the same.
You can refer xmlParserApplication from examples repo (
https://github.com/DataTorrent/examples).

Regards,
Hitesh


On Mon, Feb 6, 2017 at 11:07 AM, Ambarish Pande <
ambarish.pande2...@gmail.com> wrote:


Hello,

Is there a way to set up JAVA Serializer as the default serializer to be
used for a particular application. Currently, Kryo is the default
serializer and the library that I am using has compatibility issues with
Kryo.

Thank You.

[jira] [Assigned] (APEXCORE-640) BufferServer purge crashes when the window purged is the last available

[Sandesh (JIRA)]

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

Sandesh reassigned APEXCORE-640:


Assignee: Sandesh

> BufferServer purge crashes when the window purged is the last available
> ---
>
> Key: APEXCORE-640
> URL: https://issues.apache.org/jira/browse/APEXCORE-640
> Project: Apache Apex Core
>  Issue Type: Bug
>Reporter: Sandesh
>Assignee: Sandesh
>
> While working on the unit test of BufferServer saw this behavior, 
> purge on the last window in the buffer server crashes it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (APEXCORE-640) BufferServer purge crashes when the window purged is the last available

[Sandesh (JIRA)]

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

Sandesh updated APEXCORE-640:
-
Description: 
While working on the unit test of BufferServer saw this behavior, 

purge on the last window in the buffer server crashes it.

java.lang.IllegalArgumentException: Invalid slice: offset=2118, length=0 
array.length=4096
at com.datatorrent.netlet.util.Slice.(Slice.java:43)
at 
com.datatorrent.bufferserver.util.SerializedData.(SerializedData.java:40)
at 
com.datatorrent.bufferserver.internal.DataList$Block.purge(DataList.java:712)
at 
com.datatorrent.bufferserver.internal.DataList.purge(DataList.java:192)
at 
com.datatorrent.bufferserver.server.Server.handlePurgeRequest(Server.java:199)
at 
com.datatorrent.bufferserver.server.Server.access$1100(Server.java:65)
at 
com.datatorrent.bufferserver.server.Server$UnidentifiedClient.onMessage(Server.java:526)
at 
com.datatorrent.netlet.AbstractLengthPrependerClient.read(AbstractLengthPrependerClient.java:149)
at com.datatorrent.netlet.AbstractClient.read(AbstractClient.java:104)
at 
com.datatorrent.netlet.DefaultEventLoop.handleSelectedKey(DefaultEventLoop.java:364)
at 
com.datatorrent.netlet.OptimizedEventLoop$SelectedSelectionKeySet.forEach(OptimizedEventLoop.java:59)
at 
com.datatorrent.netlet.OptimizedEventLoop.runEventLoop(OptimizedEventLoop.java:192)
at 
com.datatorrent.netlet.OptimizedEventLoop.runEventLoop(OptimizedEventLoop.java:157)
at 
com.datatorrent.netlet.DefaultEventLoop.run(DefaultEventLoop.java:156)
at java.lang.Thread.run(Thread.java:745)

  was:
While working on the unit test of BufferServer saw this behavior, 

purge on the last window in the buffer server crashes it.


> BufferServer purge crashes when the window purged is the last available
> ---
>
> Key: APEXCORE-640
> URL: https://issues.apache.org/jira/browse/APEXCORE-640
> Project: Apache Apex Core
>  Issue Type: Bug
>Reporter: Sandesh
>Assignee: Sandesh
>
> While working on the unit test of BufferServer saw this behavior, 
> purge on the last window in the buffer server crashes it.
> java.lang.IllegalArgumentException: Invalid slice: offset=2118, length=0 
> array.length=4096
>   at com.datatorrent.netlet.util.Slice.(Slice.java:43)
>   at 
> com.datatorrent.bufferserver.util.SerializedData.(SerializedData.java:40)
>   at 
> com.datatorrent.bufferserver.internal.DataList$Block.purge(DataList.java:712)
>   at 
> com.datatorrent.bufferserver.internal.DataList.purge(DataList.java:192)
>   at 
> com.datatorrent.bufferserver.server.Server.handlePurgeRequest(Server.java:199)
>   at 
> com.datatorrent.bufferserver.server.Server.access$1100(Server.java:65)
>   at 
> com.datatorrent.bufferserver.server.Server$UnidentifiedClient.onMessage(Server.java:526)
>   at 
> com.datatorrent.netlet.AbstractLengthPrependerClient.read(AbstractLengthPrependerClient.java:149)
>   at com.datatorrent.netlet.AbstractClient.read(AbstractClient.java:104)
>   at 
> com.datatorrent.netlet.DefaultEventLoop.handleSelectedKey(DefaultEventLoop.java:364)
>   at 
> com.datatorrent.netlet.OptimizedEventLoop$SelectedSelectionKeySet.forEach(OptimizedEventLoop.java:59)
>   at 
> com.datatorrent.netlet.OptimizedEventLoop.runEventLoop(OptimizedEventLoop.java:192)
>   at 
> com.datatorrent.netlet.OptimizedEventLoop.runEventLoop(OptimizedEventLoop.java:157)
>   at 
> com.datatorrent.netlet.DefaultEventLoop.run(DefaultEventLoop.java:156)
>   at java.lang.Thread.run(Thread.java:745)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (APEXCORE-640) BufferServer purge crashes when the window purged is the last available

[Sandesh (JIRA)]

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

Sandesh updated APEXCORE-640:
-
Summary: BufferServer purge crashes when the window purged is the last 
available  (was: BufferServer purge crashes for when the window purge is the 
last available)

> BufferServer purge crashes when the window purged is the last available
> ---
>
> Key: APEXCORE-640
> URL: https://issues.apache.org/jira/browse/APEXCORE-640
> Project: Apache Apex Core
>  Issue Type: Bug
>Reporter: Sandesh
>
> While working on the unit test of BufferServer saw this behavior, 
> purge on the last window in the buffer server crashes it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] apex-core pull request #465: APEXCORE-632 BufferServer unit tests moving to ...

[sandeshh]

GitHub user sandeshh opened a pull request:

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

APEXCORE-632 BufferServer unit tests moving to Junit

1. Move the unit tests to Junit from testNg
2. Fix the failing test cases
3. Enable the test cases

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

$ git pull https://github.com/sandeshh/apex-core APEXCORE-632

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

https://github.com/apache/apex-core/pull/465.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 #465


commit 89de5f8616cfe8f61dd2ea77681c78c6e977f980
Author: Sandesh Hegde 
Date:   2017-02-02T18:49:44Z

APEXCORE-632 BufferServer unit tests moving to Junit

1. Move the unit tests to Junit from testNg
2. Fix the failing test cases
3. Enable the test cases




---
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.
---

[jira] [Assigned] (APEXCORE-637) NullPointerException in BlacklistBasedResourceRequestHandler

[Vlad Rozov (JIRA)]

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

Vlad Rozov reassigned APEXCORE-637:
---

Assignee: Vlad Rozov

> NullPointerException in BlacklistBasedResourceRequestHandler
> 
>
> Key: APEXCORE-637
> URL: https://issues.apache.org/jira/browse/APEXCORE-637
> Project: Apache Apex Core
>  Issue Type: Bug
>Reporter: Vlad Rozov
>Assignee: Vlad Rozov
>Priority: Minor
>
> Application master terminates due to NullPointerException:
> {noformat}
> 2017-02-04 08:15:37,594 INFO com.datatorrent.stram.ResourceRequestHandler: 
> Found host INVALID_HOST
> 2017-02-04 08:15:37,595 ERROR com.datatorrent.stram.StreamingAppMaster: 
> Exiting Application Master
> java.lang.NullPointerException
>   at 
> com.datatorrent.stram.BlacklistBasedResourceRequestHandler.recreateContainerRequest(BlacklistBasedResourceRequestHandler.java:108)
>   at 
> com.datatorrent.stram.BlacklistBasedResourceRequestHandler.reissueContainerRequests(BlacklistBasedResourceRequestHandler.java:79)
>   at 
> com.datatorrent.stram.StreamingAppMasterService.execute(StreamingAppMasterService.java:830)
>   at 
> com.datatorrent.stram.StreamingAppMasterService.run(StreamingAppMasterService.java:652)
>   at 
> com.datatorrent.stram.StreamingAppMaster.main(StreamingAppMaster.java:104)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (APEXMALHAR-2399) In PojoInnerJoin accumulation default constructor is directly throwing an exception which messes up in default serialization.

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/APEXMALHAR-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15853902#comment-15853902
 ] 

ASF GitHub Bot commented on APEXMALHAR-2399:


GitHub user Hitesh-Scorpio opened a pull request:

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

APEXMALHAR-2399 default constructor was directly throwing an exception

@chinmaykolhatkar please review

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

$ git pull https://github.com/Hitesh-Scorpio/apex-malhar 
APEXMALHAR-2399_PojoInnerJoin_Accumulation

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

https://github.com/apache/apex-malhar/pull/548.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 #548


commit 6cd6cabe95d3a0626d2c1274dff348841fd96a67
Author: Hitesh-Scorpio 
Date:   2017-02-06T12:19:03Z

APEXMALHAR-2399 default constructor was directly throwing an exception




> In PojoInnerJoin accumulation default constructor is directly throwing an 
> exception which messes up in default serialization.
> -
>
> Key: APEXMALHAR-2399
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2399
> Project: Apache Apex Malhar
>  Issue Type: Bug
>Reporter: Hitesh Kapoor
>Assignee: Hitesh Kapoor
>
> In PojoInnerJoin accumulation default constructor is directly throwing an 
> exception which messes up in default serialization. The exception is thrown 
> saying to specify the number of streams. Currently we only merge 2 streams so 
> there is no need to throw this exception also it messes up the serialization 
> and the applicaion can't be loaded.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] apex-malhar pull request #548: APEXMALHAR-2399 default constructor was direc...

[Hitesh-Scorpio]

GitHub user Hitesh-Scorpio opened a pull request:

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

APEXMALHAR-2399 default constructor was directly throwing an exception

@chinmaykolhatkar please review

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

$ git pull https://github.com/Hitesh-Scorpio/apex-malhar 
APEXMALHAR-2399_PojoInnerJoin_Accumulation

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

https://github.com/apache/apex-malhar/pull/548.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 #548


commit 6cd6cabe95d3a0626d2c1274dff348841fd96a67
Author: Hitesh-Scorpio 
Date:   2017-02-06T12:19:03Z

APEXMALHAR-2399 default constructor was directly throwing an exception




---
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.
---

[jira] [Commented] (APEXCORE-592) Returning description field in defaultProperties during apex cli call get-app-package-info

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/APEXCORE-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15853723#comment-15853723
 ] 

ASF GitHub Bot commented on APEXCORE-592:
-

GitHub user ajaygit158 opened a pull request:

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

APEXCORE-592 Return additional parameter description from properties.xml in 
defaultProperties for get-app-package-info command

Sample data and output : 
**properties.xml**

dt.application.FraudDetectDemo.operator.smaPerMerchant.windowSize

30
Window size



dt.application.FraudDetectDemo.operator.movingSum.attr.APPLICATION_WINDOW_COUNT

10
Window count for application


**Output : get-app-package-info package-name**
"dt.application.FraudDetectDemo.operator.smaPerMerchant.windowSize":
{ "value": "30", "description": "Window size" }
,

"dt.application.FraudDetectDemo.operator.movingSum.attr.APPLICATION_WINDOW_COUNT":
{ "value": "10", "description": null }

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

$ git pull https://github.com/ajaygit158/apex-core APEXCORE-592

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

https://github.com/apache/apex-core/pull/464.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 #464


commit 8f994c233be5f5e271e90ab1ac43fa9686acdca2
Author: ajaygit158 
Date:   2016-12-19T10:43:55Z

APEXCORE-592 Returning description field in defaultProperties during apex 
cli call get-app-package-info

commit ccd965721a27c58ae68c0ea704a445cb1f20d533
Author: ajaygit158 
Date:   2017-01-18T06:11:38Z

Changes to avoid returning unnecessary fields

commit 1523f6fa7c1d5e6f190c4c81462722fa8f4309b1
Author: ajaygit158 
Date:   2017-02-06T08:35:19Z

Changes to return description only for properties, attributes return null 
description




> Returning description field in defaultProperties during apex cli call 
> get-app-package-info
> --
>
> Key: APEXCORE-592
> URL: https://issues.apache.org/jira/browse/APEXCORE-592
> Project: Apache Apex Core
>  Issue Type: Improvement
>Reporter: Ajay Gupta
>Priority: Minor
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Currently for an operator property, only the value field is returned. The 
> operator property can have a description describing the property. This task 
> is created to return this filed for that operator property.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] apex-core pull request #464: APEXCORE-592 Return additional parameter descri...

[ajaygit158]

GitHub user ajaygit158 opened a pull request:

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

APEXCORE-592 Return additional parameter description from properties.xml in 
defaultProperties for get-app-package-info command

Sample data and output : 
**properties.xml**

dt.application.FraudDetectDemo.operator.smaPerMerchant.windowSize

30
Window size



dt.application.FraudDetectDemo.operator.movingSum.attr.APPLICATION_WINDOW_COUNT

10
Window count for application


**Output : get-app-package-info package-name**
"dt.application.FraudDetectDemo.operator.smaPerMerchant.windowSize":
{ "value": "30", "description": "Window size" }
,

"dt.application.FraudDetectDemo.operator.movingSum.attr.APPLICATION_WINDOW_COUNT":
{ "value": "10", "description": null }

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

$ git pull https://github.com/ajaygit158/apex-core APEXCORE-592

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

https://github.com/apache/apex-core/pull/464.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 #464


commit 8f994c233be5f5e271e90ab1ac43fa9686acdca2
Author: ajaygit158 
Date:   2016-12-19T10:43:55Z

APEXCORE-592 Returning description field in defaultProperties during apex 
cli call get-app-package-info

commit ccd965721a27c58ae68c0ea704a445cb1f20d533
Author: ajaygit158 
Date:   2017-01-18T06:11:38Z

Changes to avoid returning unnecessary fields

commit 1523f6fa7c1d5e6f190c4c81462722fa8f4309b1
Author: ajaygit158 
Date:   2017-02-06T08:35:19Z

Changes to return description only for properties, attributes return null 
description




---
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.
---