date:20161211

Re: Assigning Jira tickets to new contributors

2016-12-11 Thread Kai Jiang

Hi Kirk,

I am also a new contributor to GEODE project. Also, I am working on a few
issues(GEODE-2172 
GEODE-2167  GEODE-224
) . Maybe these issue
could be assigned to me.
Meanwhile, I will be appreciated if someone could review my pull requests.

JIRA id: vectorijk
Github id: vectorijk

Thanks,
Kai.



On Sat, Dec 10, 2016 at 10:57 PM, Deepak Dixit 
wrote:

> Hello Kirk,
>
> I remember some apache help document mentioning need for user to be added
> to the project group.
> May be adding user to GEODE project group will help in enabling them to
> assign issues to themselves.
>
> Can you please grant similar permission to me (details are added below) so
> I can assign JIRA issue I am working on?
> I am currently working on GEODE-2109 and just finished with GEODE-734.
>
> Detail for apache id
> Email ID: deepakdixit2...@gmail.com
> apache id: deepakddixit
>
> Thanks,
>
> Deepak
>
>
> On Dec 11, 2016 9:41 AM, "Kirk Lund"  wrote:
>
> Does anyone know what needs to be done to enable assigning a Jira ticket to
> a new contributor? Alyssa Kim filed GEODE-2203 and would like to have the
> ticket assigned to her but Jira shows either "No Matches" or "User 'Alyssa
> Kim' does not exist." -- her user id on the Apache Jira is dalyssakim.
>
> Thanks,
> Kirk
>

Build failed in Jenkins: Geode-nightly #681

2016-12-11 Thread Apache Jenkins Server

See 

--
[...truncated 2228 lines...]
:geode-cq:compileTestJavaNote: Some input files use or override a deprecated 
API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

:geode-cq:processTestResources
:geode-cq:testClasses
:geode-cq:checkMissedTests
:geode-cq:spotlessJavaCheck
:geode-cq:spotlessCheck
:geode-cq:test
:geode-cq:check
:geode-cq:build
:geode-cq:distributedTest
:geode-cq:flakyTest
:geode-cq:integrationTest
:geode-json:assemble
:geode-json:compileTestJava UP-TO-DATE
:geode-json:processTestResources UP-TO-DATE
:geode-json:testClasses UP-TO-DATE
:geode-json:checkMissedTests UP-TO-DATE
:geode-json:spotlessJavaCheck
:geode-json:spotlessCheck
:geode-json:test UP-TO-DATE
:geode-json:check
:geode-json:build
:geode-json:distributedTest UP-TO-DATE
:geode-json:flakyTest UP-TO-DATE
:geode-json:integrationTest UP-TO-DATE
:geode-junit:javadoc
:geode-junit:javadocJar
:geode-junit:sourcesJar
:geode-junit:signArchives SKIPPED
:geode-junit:assemble
:geode-junit:compileTestJava
:geode-junit:processTestResources UP-TO-DATE
:geode-junit:testClasses
:geode-junit:checkMissedTests
:geode-junit:spotlessJavaCheck
:geode-junit:spotlessCheck
:geode-junit:test
:geode-junit:check
:geode-junit:build
:geode-junit:distributedTest
:geode-junit:flakyTest
:geode-junit:integrationTest
:geode-lucene:assemble
:geode-lucene:compileTestJavaNote: Some input files use or override a 
deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

:geode-lucene:processTestResources
:geode-lucene:testClasses
:geode-lucene:checkMissedTests
:geode-lucene:spotlessJavaCheck
:geode-lucene:spotlessCheck
:geode-lucene:test
:geode-lucene:check
:geode-lucene:build
:geode-lucene:distributedTest
:geode-lucene:flakyTest
:geode-lucene:integrationTest
:geode-old-client-support:assemble
:geode-old-client-support:compileTestJava
:geode-old-client-support:processTestResources UP-TO-DATE
:geode-old-client-support:testClasses
:geode-old-client-support:checkMissedTests
:geode-old-client-support:spotlessJavaCheck
:geode-old-client-support:spotlessCheck
:geode-old-client-support:test
:geode-old-client-support:check
:geode-old-client-support:build
:geode-old-client-support:distributedTest
:geode-old-client-support:flakyTest
:geode-old-client-support:integrationTest
:geode-pulse:assemble
:geode-pulse:compileTestJavaNote: 

 uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

:geode-pulse:processTestResources
:geode-pulse:testClasses
:geode-pulse:checkMissedTests
:geode-pulse:spotlessJavaCheck
:geode-pulse:spotlessCheck
:geode-pulse:test
:geode-pulse:check
:geode-pulse:build
:geode-pulse:distributedTest
:geode-pulse:flakyTest
:geode-pulse:integrationTest
:geode-rebalancer:assemble
:geode-rebalancer:compileTestJava
:geode-rebalancer:processTestResources UP-TO-DATE
:geode-rebalancer:testClasses
:geode-rebalancer:checkMissedTests
:geode-rebalancer:spotlessJavaCheck
:geode-rebalancer:spotlessCheck
:geode-rebalancer:test
:geode-rebalancer:check
:geode-rebalancer:build
:geode-rebalancer:distributedTest
:geode-rebalancer:flakyTest
:geode-rebalancer:integrationTest
:geode-wan:assemble
:geode-wan:compileTestJavaNote: Some input files use or override a deprecated 
API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

:geode-wan:processTestResources
:geode-wan:testClasses
:geode-wan:checkMissedTests
:geode-wan:spotlessJavaCheck
:geode-wan:spotlessCheck
:geode-wan:test
:geode-wan:check
:geode-wan:build
:geode-wan:distributedTest
:geode-wan:flakyTest
:geode-wan:integrationTest
:geode-web:assemble
:geode-web:compileTestJavaNote: Some input files use or override a deprecated 
API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

:geode-web:processTestResources UP-TO-DATE
:geode-web:testClasses
:geode-web:checkMissedTests
:geode-web:spotlessJavaCheck
:geode-web:spotlessCheck
:geode-web:test
:geode-web:check
:geode-web:build
:geode-web:distributedTest
:geode-web:flakyTest
:geode-web:integrationTest
:geode-web-api:assemble
:geode-web-api:compileTestJava UP-TO-DATE
:geode-web-api:processTestResources UP-TO-DATE
:geode-web-api:testClasses UP-TO-DATE
:geode-web-api:checkMissedTests UP-TO-DATE
:geode-web-api:spotlessJavaCheck
:geode-web-api:spotlessCheck
:geode-web-api:test UP

[jira] [Assigned] (GEODE-2061) Remove PdxInstanceInputStream

2016-12-11 Thread Avinash Dongre (JIRA)


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

Avinash Dongre reassigned GEODE-2061:
-

Assignee: Avinash Dongre

> Remove PdxInstanceInputStream
> -
>
> Key: GEODE-2061
> URL: https://issues.apache.org/jira/browse/GEODE-2061
> Project: Geode
>  Issue Type: Improvement
>  Components: serialization
>Reporter: Bruce Schuchardt
>Assignee: Avinash Dongre
>
> This class should be removed and its uses replaced with its superclass 
> PdxInputStream.  None of the methods it contains differs from the superclass 
> implementation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Build failed in Jenkins: Geode-nightly #680

2016-12-11 Thread Jinmei Liao

This build failed probably because of our change of some of the cluster
config code. Those are not failing in concourse though. Will look into this
more.

On Sat, Dec 10, 2016 at 7:48 AM, Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> See 
>
> Changes:
>
> [adongre] GEODE-1984: Fix Issue Make GatewaySender destroy a public API
>
> [adongre] GEODE-1984: Addressed review comments, Removed copy pasted
> repeating
>
> [jiliao] [GEODE-2196] Add test for Cluster Config. Refactor
>
> [upthewaterspout] GEODE-2186: Changing the gateway status to only looking
> running status
>
> [abaker] Update website release references to remove incubator
>
> [bschuchardt] GEODE-2193 a member is kicked out immediately after joining
>
> --
> [...truncated 1616 lines...]
> :geode-cq:compileTestJavaNote: Some input files use or override a
> deprecated API.
> Note: Recompile with -Xlint:deprecation for details.
> Note: Some input files use unchecked or unsafe operations.
> Note: Recompile with -Xlint:unchecked for details.
>
> :geode-cq:processTestResources
> :geode-cq:testClasses
> :geode-cq:checkMissedTests
> :geode-cq:spotlessJavaCheck
> :geode-cq:spotlessCheck
> :geode-cq:test
> :geode-cq:check
> :geode-cq:build
> :geode-cq:distributedTest
> :geode-cq:flakyTest
> :geode-cq:integrationTest
> :geode-json:assemble
> :geode-json:compileTestJava UP-TO-DATE
> :geode-json:processTestResources UP-TO-DATE
> :geode-json:testClasses UP-TO-DATE
> :geode-json:checkMissedTests UP-TO-DATE
> :geode-json:spotlessJavaCheck
> :geode-json:spotlessCheck
> :geode-json:test UP-TO-DATE
> :geode-json:check
> :geode-json:build
> :geode-json:distributedTest UP-TO-DATE
> :geode-json:flakyTest UP-TO-DATE
> :geode-json:integrationTest UP-TO-DATE
> :geode-junit:javadoc
> :geode-junit:javadocJar
> :geode-junit:sourcesJar
> :geode-junit:signArchives SKIPPED
> :geode-junit:assemble
> :geode-junit:compileTestJava
> :geode-junit:processTestResources UP-TO-DATE
> :geode-junit:testClasses
> :geode-junit:checkMissedTests
> :geode-junit:spotlessJavaCheck
> :geode-junit:spotlessCheck
> :geode-junit:test
> :geode-junit:check
> :geode-junit:build
> :geode-junit:distributedTest
> :geode-junit:flakyTest
> :geode-junit:integrationTest
> :geode-lucene:assemble
> :geode-lucene:compileTestJavaNote: Some input files use or override a
> deprecated API.
> Note: Recompile with -Xlint:deprecation for details.
> Note: Some input files use unchecked or unsafe operations.
> Note: Recompile with -Xlint:unchecked for details.
>
> :geode-lucene:processTestResources
> :geode-lucene:testClasses
> :geode-lucene:checkMissedTests
> :geode-lucene:spotlessJavaCheck
> :geode-lucene:spotlessCheck
> :geode-lucene:test
> :geode-lucene:check
> :geode-lucene:build
> :geode-lucene:distributedTest
> :geode-lucene:flakyTest
> :geode-lucene:integrationTest
> :geode-old-client-support:assemble
> :geode-old-client-support:compileTestJava
> :geode-old-client-support:processTestResources UP-TO-DATE
> :geode-old-client-support:testClasses
> :geode-old-client-support:checkMissedTests
> :geode-old-client-support:spotlessJavaCheck
> :geode-old-client-support:spotlessCheck
> :geode-old-client-support:test
> :geode-old-client-support:check
> :geode-old-client-support:build
> :geode-old-client-support:distributedTest
> :geode-old-client-support:flakyTest
> :geode-old-client-support:integrationTest
> :geode-pulse:assemble
> :geode-pulse:compileTestJavaNote:  job/Geode-nightly/ws/geode-pulse/src/test/java/org/
> apache/geode/tools/pulse/tests/ui/PulseBase.java> uses or overrides a
> deprecated API.
> Note: Recompile with -Xlint:deprecation for details.
> Note: Some input files use unchecked or unsafe operations.
> Note: Recompile with -Xlint:unchecked for details.
>
> :geode-pulse:processTestResources
> :geode-pulse:testClasses
> :geode-pulse:checkMissedTests
> :geode-pulse:spotlessJavaCheck
> :geode-pulse:spotlessCheck
> :geode-pulse:test
> :geode-pulse:check
> :geode-pulse:build
> :geode-pulse:distributedTest
> :geode-pulse:flakyTest
> :geode-pulse:integrationTest
> :geode-rebalancer:assemble
> :geode-rebalancer:compileTestJava
> :geode-rebalancer:processTestResources UP-TO-DATE
> :geode-rebalancer:testClasses
> :geode-rebalancer:checkMissedTests
> :geode-rebalancer:spotlessJavaCheck
> :geode-rebalancer:spotlessCheck
> :geode-rebalancer:test
> :geode-rebalancer:check
> :geode-rebalancer:build
> :geode-rebalancer:distributedTest
> :geode-rebalancer:flakyTest
> :geode-rebalancer:integrationTest
> :geode-wan:assemble
> :geode-wan:compileTestJavaNote: Some input files use or override a
> deprecated API.
> Note: Recompile with -Xlint:deprecation for details.
> Note: Some input files use unchecked or unsafe operations.
> Note: Recompile with -Xlint:unchecked for details.
>
> :geode-wan:processTestResources
> :geode-wan:testClasses
> :geode-wan:checkMissedTests
> :geode-wan:spotlessJav

Re: Build failed in Jenkins: Geode-nightly #680

2016-12-11 Thread Mark Bretl

Are these Concourse runs available to the community?

--Mark
On Sun, Dec 11, 2016 at 12:38 PM Jinmei Liao  wrote:

> This build failed probably because of our change of some of the cluster
>
> config code. Those are not failing in concourse though. Will look into this
>
> more.
>
>
>
> On Sat, Dec 10, 2016 at 7:48 AM, Apache Jenkins Server <
>
> jenk...@builds.apache.org> wrote:
>
>
>
> > See 
>
> >
>
> > Changes:
>
> >
>
> > [adongre] GEODE-1984: Fix Issue Make GatewaySender destroy a public API
>
> >
>
> > [adongre] GEODE-1984: Addressed review comments, Removed copy pasted
>
> > repeating
>
> >
>
> > [jiliao] [GEODE-2196] Add test for Cluster Config. Refactor
>
> >
>
> > [upthewaterspout] GEODE-2186: Changing the gateway status to only looking
>
> > running status
>
> >
>
> > [abaker] Update website release references to remove incubator
>
> >
>
> > [bschuchardt] GEODE-2193 a member is kicked out immediately after joining
>
> >
>
> > --
>
> > [...truncated 1616 lines...]
>
> > :geode-cq:compileTestJavaNote: Some input files use or override a
>
> > deprecated API.
>
> > Note: Recompile with -Xlint:deprecation for details.
>
> > Note: Some input files use unchecked or unsafe operations.
>
> > Note: Recompile with -Xlint:unchecked for details.
>
> >
>
> > :geode-cq:processTestResources
>
> > :geode-cq:testClasses
>
> > :geode-cq:checkMissedTests
>
> > :geode-cq:spotlessJavaCheck
>
> > :geode-cq:spotlessCheck
>
> > :geode-cq:test
>
> > :geode-cq:check
>
> > :geode-cq:build
>
> > :geode-cq:distributedTest
>
> > :geode-cq:flakyTest
>
> > :geode-cq:integrationTest
>
> > :geode-json:assemble
>
> > :geode-json:compileTestJava UP-TO-DATE
>
> > :geode-json:processTestResources UP-TO-DATE
>
> > :geode-json:testClasses UP-TO-DATE
>
> > :geode-json:checkMissedTests UP-TO-DATE
>
> > :geode-json:spotlessJavaCheck
>
> > :geode-json:spotlessCheck
>
> > :geode-json:test UP-TO-DATE
>
> > :geode-json:check
>
> > :geode-json:build
>
> > :geode-json:distributedTest UP-TO-DATE
>
> > :geode-json:flakyTest UP-TO-DATE
>
> > :geode-json:integrationTest UP-TO-DATE
>
> > :geode-junit:javadoc
>
> > :geode-junit:javadocJar
>
> > :geode-junit:sourcesJar
>
> > :geode-junit:signArchives SKIPPED
>
> > :geode-junit:assemble
>
> > :geode-junit:compileTestJava
>
> > :geode-junit:processTestResources UP-TO-DATE
>
> > :geode-junit:testClasses
>
> > :geode-junit:checkMissedTests
>
> > :geode-junit:spotlessJavaCheck
>
> > :geode-junit:spotlessCheck
>
> > :geode-junit:test
>
> > :geode-junit:check
>
> > :geode-junit:build
>
> > :geode-junit:distributedTest
>
> > :geode-junit:flakyTest
>
> > :geode-junit:integrationTest
>
> > :geode-lucene:assemble
>
> > :geode-lucene:compileTestJavaNote: Some input files use or override a
>
> > deprecated API.
>
> > Note: Recompile with -Xlint:deprecation for details.
>
> > Note: Some input files use unchecked or unsafe operations.
>
> > Note: Recompile with -Xlint:unchecked for details.
>
> >
>
> > :geode-lucene:processTestResources
>
> > :geode-lucene:testClasses
>
> > :geode-lucene:checkMissedTests
>
> > :geode-lucene:spotlessJavaCheck
>
> > :geode-lucene:spotlessCheck
>
> > :geode-lucene:test
>
> > :geode-lucene:check
>
> > :geode-lucene:build
>
> > :geode-lucene:distributedTest
>
> > :geode-lucene:flakyTest
>
> > :geode-lucene:integrationTest
>
> > :geode-old-client-support:assemble
>
> > :geode-old-client-support:compileTestJava
>
> > :geode-old-client-support:processTestResources UP-TO-DATE
>
> > :geode-old-client-support:testClasses
>
> > :geode-old-client-support:checkMissedTests
>
> > :geode-old-client-support:spotlessJavaCheck
>
> > :geode-old-client-support:spotlessCheck
>
> > :geode-old-client-support:test
>
> > :geode-old-client-support:check
>
> > :geode-old-client-support:build
>
> > :geode-old-client-support:distributedTest
>
> > :geode-old-client-support:flakyTest
>
> > :geode-old-client-support:integrationTest
>
> > :geode-pulse:assemble
>
> > :geode-pulse:compileTestJavaNote: 
> > job/Geode-nightly/ws/geode-pulse/src/test/java/org/
>
> > apache/geode/tools/pulse/tests/ui/PulseBase.java> uses or overrides a
>
> > deprecated API.
>
> > Note: Recompile with -Xlint:deprecation for details.
>
> > Note: Some input files use unchecked or unsafe operations.
>
> > Note: Recompile with -Xlint:unchecked for details.
>
> >
>
> > :geode-pulse:processTestResources
>
> > :geode-pulse:testClasses
>
> > :geode-pulse:checkMissedTests
>
> > :geode-pulse:spotlessJavaCheck
>
> > :geode-pulse:spotlessCheck
>
> > :geode-pulse:test
>
> > :geode-pulse:check
>
> > :geode-pulse:build
>
> > :geode-pulse:distributedTest
>
> > :geode-pulse:flakyTest
>
> > :geode-pulse:integrationTest
>
> > :geode-rebalancer:assemble
>
> > :geode-rebalancer:compileTestJava
>
> > :geode-rebalancer:processTestResources UP-TO-DATE
>
> > :geode-rebalancer:testClasses
>
> > :geode-rebalancer:checkMissedTests
>
> > :geode-

[jira] [Commented] (GEODE-2203) gfsh status locator/server - Give more descriptive output on empty parameter

2016-12-11 Thread Jinmei Liao (JIRA)


[ 
https://issues.apache.org/jira/browse/GEODE-2203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15740382#comment-15740382
 ] 

Jinmei Liao commented on GEODE-2203:


Here is my branch https://github.com/jinmeiliao/geode/tree/GEODE-1912

> gfsh status locator/server - Give more descriptive output on empty parameter
> 
>
> Key: GEODE-2203
> URL: https://issues.apache.org/jira/browse/GEODE-2203
> Project: Geode
>  Issue Type: Improvement
>  Components: gfsh
>Reporter: Alyssa Kim
>Assignee: Mark Bretl
>Priority: Minor
>
> Currently, executing some status commands in gfsh without valid parameters 
> gives a vague explanation/output that might be misleading. Although we have 
> help  for usage description, displaying 'null' as an output 
> might not be the best idea.
> Current Result
> {code}
> gfsh>status locator
> null
> {code}
> {code}
> gfsh>status server
> Server in 
> C:\Users\XXX\git\incubator-geode\geode-assembly\build\install\apache-geode\bin
>  on null is currently not responding.
> {code}
> Improvement
> {code}
> gfsh>status locator
> SYNTAX
> status locator [--name=value] [--host=value] [--port=value] [--pid=value]
> Use help status locator to display detailed usage information
> {code}
> {code}
> gfsh>status server
> SYNTAX
> status server [--name=value] [--pid=value] [--dir=value]
> Use help status server to display detailed usage information
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (GEODE-2203) gfsh status locator/server - Give more descriptive output on empty parameter

2016-12-11 Thread Alyssa Kim (JIRA)


[ 
https://issues.apache.org/jira/browse/GEODE-2203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15740724#comment-15740724
 ] 

Alyssa Kim commented on GEODE-2203:
---

[~klund] [~jinmeiliao] Thanks for the explanation and the url. 
 What should be the workaround in this case? It makes sense if I can work on 
top of GEODE-1912. Can I create this branch(GEODE-2203) and merge GEODE-1912 
into it to avoid potential conflict or is there other way around?
Thanks,

> gfsh status locator/server - Give more descriptive output on empty parameter
> 
>
> Key: GEODE-2203
> URL: https://issues.apache.org/jira/browse/GEODE-2203
> Project: Geode
>  Issue Type: Improvement
>  Components: gfsh
>Reporter: Alyssa Kim
>Assignee: Mark Bretl
>Priority: Minor
>
> Currently, executing some status commands in gfsh without valid parameters 
> gives a vague explanation/output that might be misleading. Although we have 
> help  for usage description, displaying 'null' as an output 
> might not be the best idea.
> Current Result
> {code}
> gfsh>status locator
> null
> {code}
> {code}
> gfsh>status server
> Server in 
> C:\Users\XXX\git\incubator-geode\geode-assembly\build\install\apache-geode\bin
>  on null is currently not responding.
> {code}
> Improvement
> {code}
> gfsh>status locator
> SYNTAX
> status locator [--name=value] [--host=value] [--port=value] [--pid=value]
> Use help status locator to display detailed usage information
> {code}
> {code}
> gfsh>status server
> SYNTAX
> status server [--name=value] [--pid=value] [--dir=value]
> Use help status server to display detailed usage information
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (GEODE-2172) CustomConfigWithCacheIntegrationTest fails with AssertionError on Windows

2016-12-11 Thread William Markito Oliveira (JIRA)


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

William Markito Oliveira updated GEODE-2172:

Assignee: Kai Jiang

> CustomConfigWithCacheIntegrationTest fails with AssertionError on Windows
> -
>
> Key: GEODE-2172
> URL: https://issues.apache.org/jira/browse/GEODE-2172
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Affects Versions: 1.0.0-incubating
> Environment: Windows
>Reporter: Kirk Lund
>Assignee: Kai Jiang
>  Labels: IntegrationTest, Windows
>
> cacheLogWriterMessageShouldMatchCustomConfig fails with AssertionError. See 
> attached file for full output from the test.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Assigning Jira tickets to new contributors

2016-12-11 Thread William Markito Oliveira

I've just add all 3 (vectorijk, deepakddixit, dalyssakim) as "contributors"
to the Geode JIRA project, but in the past we had problems with people not
being able to "self-assign" JIRAs if they're not in the "committers" group.

The workaround was to include them into the committers group on JIRA, which
don't necessary give them commit privilege on the codebase, just on JIRA.
Alternatively now that we graduated we could try fixing the role
"contributor" of JIRA to at least allow people to assign JIRAs to
themselves.

Please give it a try now and see if you can assign the tickets to you,
otherwise let us know.   Thanks!

On Sun, Dec 11, 2016 at 5:35 AM, Kai Jiang  wrote:

> Hi Kirk,
>
> I am also a new contributor to GEODE project. Also, I am working on a few
> issues(GEODE-2172 
> GEODE-2167  GEODE-224
> ) . Maybe these issue
> could be assigned to me.
> Meanwhile, I will be appreciated if someone could review my pull requests.
>
> JIRA id: vectorijk
> Github id: vectorijk
>
> Thanks,
> Kai.
>
>
>
> On Sat, Dec 10, 2016 at 10:57 PM, Deepak Dixit 
> wrote:
>
> > Hello Kirk,
> >
> > I remember some apache help document mentioning need for user to be added
> > to the project group.
> > May be adding user to GEODE project group will help in enabling them to
> > assign issues to themselves.
> >
> > Can you please grant similar permission to me (details are added below)
> so
> > I can assign JIRA issue I am working on?
> > I am currently working on GEODE-2109 and just finished with GEODE-734.
> >
> > Detail for apache id
> > Email ID: deepakdixit2...@gmail.com
> > apache id: deepakddixit
> >
> > Thanks,
> >
> > Deepak
> >
> >
> > On Dec 11, 2016 9:41 AM, "Kirk Lund"  wrote:
> >
> > Does anyone know what needs to be done to enable assigning a Jira ticket
> to
> > a new contributor? Alyssa Kim filed GEODE-2203 and would like to have the
> > ticket assigned to her but Jira shows either "No Matches" or "User
> 'Alyssa
> > Kim' does not exist." -- her user id on the Apache Jira is dalyssakim.
> >
> > Thanks,
> > Kirk
> >
>

-- 
~/William

[jira] [Assigned] (GEODE-2203) gfsh status locator/server - Give more descriptive output on empty parameter

2016-12-11 Thread Alyssa Kim (JIRA)


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

Alyssa Kim reassigned GEODE-2203:
-

Assignee: Alyssa Kim  (was: Mark Bretl)

> gfsh status locator/server - Give more descriptive output on empty parameter
> 
>
> Key: GEODE-2203
> URL: https://issues.apache.org/jira/browse/GEODE-2203
> Project: Geode
>  Issue Type: Improvement
>  Components: gfsh
>Reporter: Alyssa Kim
>Assignee: Alyssa Kim
>Priority: Minor
>
> Currently, executing some status commands in gfsh without valid parameters 
> gives a vague explanation/output that might be misleading. Although we have 
> help  for usage description, displaying 'null' as an output 
> might not be the best idea.
> Current Result
> {code}
> gfsh>status locator
> null
> {code}
> {code}
> gfsh>status server
> Server in 
> C:\Users\XXX\git\incubator-geode\geode-assembly\build\install\apache-geode\bin
>  on null is currently not responding.
> {code}
> Improvement
> {code}
> gfsh>status locator
> SYNTAX
> status locator [--name=value] [--host=value] [--port=value] [--pid=value]
> Use help status locator to display detailed usage information
> {code}
> {code}
> gfsh>status server
> SYNTAX
> status server [--name=value] [--pid=value] [--dir=value]
> Use help status server to display detailed usage information
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Assigning Jira tickets to new contributors

2016-12-11 Thread Alyssa Kim

Now, I am able to assign tickets to myself.
Thank you very much for the help :) !!

Best Regards

On Sun, Dec 11, 2016 at 6:30 PM, William Markito Oliveira <
william.mark...@gmail.com> wrote:

> I've just add all 3 (vectorijk, deepakddixit, dalyssakim) as "contributors"
> to the Geode JIRA project, but in the past we had problems with people not
> being able to "self-assign" JIRAs if they're not in the "committers" group.
>
> The workaround was to include them into the committers group on JIRA, which
> don't necessary give them commit privilege on the codebase, just on JIRA.
> Alternatively now that we graduated we could try fixing the role
> "contributor" of JIRA to at least allow people to assign JIRAs to
> themselves.
>
> Please give it a try now and see if you can assign the tickets to you,
> otherwise let us know.   Thanks!
>
> On Sun, Dec 11, 2016 at 5:35 AM, Kai Jiang  wrote:
>
> > Hi Kirk,
> >
> > I am also a new contributor to GEODE project. Also, I am working on a few
> > issues(GEODE-2172 
> > GEODE-2167  GEODE-224
> > ) . Maybe these issue
> > could be assigned to me.
> > Meanwhile, I will be appreciated if someone could review my pull
> requests.
> >
> > JIRA id: vectorijk
> > Github id: vectorijk
> >
> > Thanks,
> > Kai.
> >
> >
> >
> > On Sat, Dec 10, 2016 at 10:57 PM, Deepak Dixit <
> deepakdixit2...@gmail.com>
> > wrote:
> >
> > > Hello Kirk,
> > >
> > > I remember some apache help document mentioning need for user to be
> added
> > > to the project group.
> > > May be adding user to GEODE project group will help in enabling them to
> > > assign issues to themselves.
> > >
> > > Can you please grant similar permission to me (details are added below)
> > so
> > > I can assign JIRA issue I am working on?
> > > I am currently working on GEODE-2109 and just finished with GEODE-734.
> > >
> > > Detail for apache id
> > > Email ID: deepakdixit2...@gmail.com
> > > apache id: deepakddixit
> > >
> > > Thanks,
> > >
> > > Deepak
> > >
> > >
> > > On Dec 11, 2016 9:41 AM, "Kirk Lund"  wrote:
> > >
> > > Does anyone know what needs to be done to enable assigning a Jira
> ticket
> > to
> > > a new contributor? Alyssa Kim filed GEODE-2203 and would like to have
> the
> > > ticket assigned to her but Jira shows either "No Matches" or "User
> > 'Alyssa
> > > Kim' does not exist." -- her user id on the Apache Jira is dalyssakim.
> > >
> > > Thanks,
> > > Kirk
> > >
> >
>
>
>
> --
> ~/William
>

Re: Assigning Jira tickets to new contributors

2016-12-11 Thread Kirk Lund

Thanks William!

On Sun, Dec 11, 2016 at 6:30 PM William Markito Oliveira <
william.mark...@gmail.com> wrote:

> I've just add all 3 (vectorijk, deepakddixit, dalyssakim) as "contributors"
>
> to the Geode JIRA project, but in the past we had problems with people not
>
> being able to "self-assign" JIRAs if they're not in the "committers" group.
>
>
>
> The workaround was to include them into the committers group on JIRA, which
>
> don't necessary give them commit privilege on the codebase, just on JIRA.
>
> Alternatively now that we graduated we could try fixing the role
>
> "contributor" of JIRA to at least allow people to assign JIRAs to
>
> themselves.
>
>
>
> Please give it a try now and see if you can assign the tickets to you,
>
> otherwise let us know.   Thanks!
>
>
>
> On Sun, Dec 11, 2016 at 5:35 AM, Kai Jiang  wrote:
>
>
>
> > Hi Kirk,
>
> >
>
> > I am also a new contributor to GEODE project. Also, I am working on a few
>
> > issues(GEODE-2172 
>
> > GEODE-2167  GEODE-224
>
> > ) . Maybe these issue
>
> > could be assigned to me.
>
> > Meanwhile, I will be appreciated if someone could review my pull
> requests.
>
> >
>
> > JIRA id: vectorijk
>
> > Github id: vectorijk
>
> >
>
> > Thanks,
>
> > Kai.
>
> >
>
> >
>
> >
>
> > On Sat, Dec 10, 2016 at 10:57 PM, Deepak Dixit <
> deepakdixit2...@gmail.com>
>
> > wrote:
>
> >
>
> > > Hello Kirk,
>
> > >
>
> > > I remember some apache help document mentioning need for user to be
> added
>
> > > to the project group.
>
> > > May be adding user to GEODE project group will help in enabling them to
>
> > > assign issues to themselves.
>
> > >
>
> > > Can you please grant similar permission to me (details are added below)
>
> > so
>
> > > I can assign JIRA issue I am working on?
>
> > > I am currently working on GEODE-2109 and just finished with GEODE-734.
>
> > >
>
> > > Detail for apache id
>
> > > Email ID: deepakdixit2...@gmail.com
>
> > > apache id: deepakddixit
>
> > >
>
> > > Thanks,
>
> > >
>
> > > Deepak
>
> > >
>
> > >
>
> > > On Dec 11, 2016 9:41 AM, "Kirk Lund"  wrote:
>
> > >
>
> > > Does anyone know what needs to be done to enable assigning a Jira
> ticket
>
> > to
>
> > > a new contributor? Alyssa Kim filed GEODE-2203 and would like to have
> the
>
> > > ticket assigned to her but Jira shows either "No Matches" or "User
>
> > 'Alyssa
>
> > > Kim' does not exist." -- her user id on the Apache Jira is dalyssakim.
>
> > >
>
> > > Thanks,
>
> > > Kirk
>
> > >
>
> >
>
>
>
>
>
>
>
> --
>
> ~/William
>
>

Re: Assigning Jira tickets to new contributors

2016-12-11 Thread William Markito Oliveira

Great! So assigning people to the "contributors" role is good enough for
this, glad it worked!

On Sun, Dec 11, 2016 at 6:51 PM Kirk Lund  wrote:

> Thanks William!
>
> On Sun, Dec 11, 2016 at 6:30 PM William Markito Oliveira <
> william.mark...@gmail.com> wrote:
>
> > I've just add all 3 (vectorijk, deepakddixit, dalyssakim) as
> "contributors"
> >
> > to the Geode JIRA project, but in the past we had problems with people
> not
> >
> > being able to "self-assign" JIRAs if they're not in the "committers"
> group.
> >
> >
> >
> > The workaround was to include them into the committers group on JIRA,
> which
> >
> > don't necessary give them commit privilege on the codebase, just on JIRA.
> >
> > Alternatively now that we graduated we could try fixing the role
> >
> > "contributor" of JIRA to at least allow people to assign JIRAs to
> >
> > themselves.
> >
> >
> >
> > Please give it a try now and see if you can assign the tickets to you,
> >
> > otherwise let us know.   Thanks!
> >
> >
> >
> > On Sun, Dec 11, 2016 at 5:35 AM, Kai Jiang  wrote:
> >
> >
> >
> > > Hi Kirk,
> >
> > >
> >
> > > I am also a new contributor to GEODE project. Also, I am working on a
> few
> >
> > > issues(GEODE-2172 
> >
> > > GEODE-2167 
> GEODE-224
> >
> > > ) . Maybe these issue
> >
> > > could be assigned to me.
> >
> > > Meanwhile, I will be appreciated if someone could review my pull
> > requests.
> >
> > >
> >
> > > JIRA id: vectorijk
> >
> > > Github id: vectorijk
> >
> > >
> >
> > > Thanks,
> >
> > > Kai.
> >
> > >
> >
> > >
> >
> > >
> >
> > > On Sat, Dec 10, 2016 at 10:57 PM, Deepak Dixit <
> > deepakdixit2...@gmail.com>
> >
> > > wrote:
> >
> > >
> >
> > > > Hello Kirk,
> >
> > > >
> >
> > > > I remember some apache help document mentioning need for user to be
> > added
> >
> > > > to the project group.
> >
> > > > May be adding user to GEODE project group will help in enabling them
> to
> >
> > > > assign issues to themselves.
> >
> > > >
> >
> > > > Can you please grant similar permission to me (details are added
> below)
> >
> > > so
> >
> > > > I can assign JIRA issue I am working on?
> >
> > > > I am currently working on GEODE-2109 and just finished with
> GEODE-734.
> >
> > > >
> >
> > > > Detail for apache id
> >
> > > > Email ID: deepakdixit2...@gmail.com
> >
> > > > apache id: deepakddixit
> >
> > > >
> >
> > > > Thanks,
> >
> > > >
> >
> > > > Deepak
> >
> > > >
> >
> > > >
> >
> > > > On Dec 11, 2016 9:41 AM, "Kirk Lund"  wrote:
> >
> > > >
> >
> > > > Does anyone know what needs to be done to enable assigning a Jira
> > ticket
> >
> > > to
> >
> > > > a new contributor? Alyssa Kim filed GEODE-2203 and would like to have
> > the
> >
> > > > ticket assigned to her but Jira shows either "No Matches" or "User
> >
> > > 'Alyssa
> >
> > > > Kim' does not exist." -- her user id on the Apache Jira is
> dalyssakim.
> >
> > > >
> >
> > > > Thanks,
> >
> > > > Kirk
> >
> > > >
> >
> > >
> >
> >
> >
> >
> >
> >
> >
> > --
> >
> > ~/William
> >
> >
>

[jira] [Assigned] (GEODE-2109) calling submit on ExecutionService can cause exceptions to be lost

2016-12-11 Thread Deepak Dixit (JIRA)


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

Deepak Dixit reassigned GEODE-2109:
---

Assignee: Deepak Dixit

> calling submit on ExecutionService can cause exceptions to be lost
> --
>
> Key: GEODE-2109
> URL: https://issues.apache.org/jira/browse/GEODE-2109
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Reporter: Darrel Schneider
>Assignee: Deepak Dixit
>
> Geode has a number of places that call submit on ExecutionService. The submit 
> method returns a Future object. If the caller makes sure it calls "get" on 
> the Future then all is well. But in many places geode is not calling get. In 
> that case if the Runnable that was submitted throws an exception it gets 
> stored in the get and never logged. This can make it very hard to diagnose 
> problems.
> If the caller does not want to call get on the returned Future then it should 
> instead call the "execute" method. In that case the exception will be 
> unhandled and the unhandled exception handler code we have on the 
> LoggingThreadGroup class will cause the exception to be logged.
> Here are the places that should be changed to use execute instead of submit:
> org.apache.geode.internal.util.concurrent.CustomEntryConcurrentHashMap.clear()
> org.apache.geode.internal.cache.DiskStoreImpl.executeDiskStoreTask(Runnable)
> org.apache.geode.internal.cache.lru.HeapEvictor.onEvent(MemoryEvent)
> org.apache.geode.distributed.internal.InternalLocator.restartWithDS(InternalDistributedSystem,
>  GemFireCacheImpl)
> org.apache.geode.distributed.internal.FunctionExecutionPooledExecutor.FunctionExecutionPooledExecutor(BlockingQueue,
>  int, PoolStatHelper, ThreadFactory, int, boolean)
> org.apache.geode.internal.cache.PRHARedundancyProvider.scheduleCreateMissingBuckets()
> org.apache.geode.distributed.internal.InternalLocator.startSharedConfigurationService(GemFireCacheImpl)
> org.apache.geode.cache.client.internal.SingleHopClientExecutor.submitTask(Runnable)
> org.apache.geode.management.internal.FederatingManager.submitTask(Callable)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Assigning Jira tickets to new contributors

2016-12-11 Thread Deepak Dixit

Thanks William :)
I am able to assign JIRA on my apache id.


On Mon, Dec 12, 2016 at 8:29 AM, William Markito Oliveira <
william.mark...@gmail.com> wrote:

> Great! So assigning people to the "contributors" role is good enough for
> this, glad it worked!
>
> On Sun, Dec 11, 2016 at 6:51 PM Kirk Lund  wrote:
>
> > Thanks William!
> >
> > On Sun, Dec 11, 2016 at 6:30 PM William Markito Oliveira <
> > william.mark...@gmail.com> wrote:
> >
> > > I've just add all 3 (vectorijk, deepakddixit, dalyssakim) as
> > "contributors"
> > >
> > > to the Geode JIRA project, but in the past we had problems with people
> > not
> > >
> > > being able to "self-assign" JIRAs if they're not in the "committers"
> > group.
> > >
> > >
> > >
> > > The workaround was to include them into the committers group on JIRA,
> > which
> > >
> > > don't necessary give them commit privilege on the codebase, just on
> JIRA.
> > >
> > > Alternatively now that we graduated we could try fixing the role
> > >
> > > "contributor" of JIRA to at least allow people to assign JIRAs to
> > >
> > > themselves.
> > >
> > >
> > >
> > > Please give it a try now and see if you can assign the tickets to you,
> > >
> > > otherwise let us know.   Thanks!
> > >
> > >
> > >
> > > On Sun, Dec 11, 2016 at 5:35 AM, Kai Jiang  wrote:
> > >
> > >
> > >
> > > > Hi Kirk,
> > >
> > > >
> > >
> > > > I am also a new contributor to GEODE project. Also, I am working on a
> > few
> > >
> > > > issues(GEODE-2172 
> > >
> > > > GEODE-2167 
> > GEODE-224
> > >
> > > > ) . Maybe these
> issue
> > >
> > > > could be assigned to me.
> > >
> > > > Meanwhile, I will be appreciated if someone could review my pull
> > > requests.
> > >
> > > >
> > >
> > > > JIRA id: vectorijk
> > >
> > > > Github id: vectorijk
> > >
> > > >
> > >
> > > > Thanks,
> > >
> > > > Kai.
> > >
> > > >
> > >
> > > >
> > >
> > > >
> > >
> > > > On Sat, Dec 10, 2016 at 10:57 PM, Deepak Dixit <
> > > deepakdixit2...@gmail.com>
> > >
> > > > wrote:
> > >
> > > >
> > >
> > > > > Hello Kirk,
> > >
> > > > >
> > >
> > > > > I remember some apache help document mentioning need for user to be
> > > added
> > >
> > > > > to the project group.
> > >
> > > > > May be adding user to GEODE project group will help in enabling
> them
> > to
> > >
> > > > > assign issues to themselves.
> > >
> > > > >
> > >
> > > > > Can you please grant similar permission to me (details are added
> > below)
> > >
> > > > so
> > >
> > > > > I can assign JIRA issue I am working on?
> > >
> > > > > I am currently working on GEODE-2109 and just finished with
> > GEODE-734.
> > >
> > > > >
> > >
> > > > > Detail for apache id
> > >
> > > > > Email ID: deepakdixit2...@gmail.com
> > >
> > > > > apache id: deepakddixit
> > >
> > > > >
> > >
> > > > > Thanks,
> > >
> > > > >
> > >
> > > > > Deepak
> > >
> > > > >
> > >
> > > > >
> > >
> > > > > On Dec 11, 2016 9:41 AM, "Kirk Lund"  wrote:
> > >
> > > > >
> > >
> > > > > Does anyone know what needs to be done to enable assigning a Jira
> > > ticket
> > >
> > > > to
> > >
> > > > > a new contributor? Alyssa Kim filed GEODE-2203 and would like to
> have
> > > the
> > >
> > > > > ticket assigned to her but Jira shows either "No Matches" or "User
> > >
> > > > 'Alyssa
> > >
> > > > > Kim' does not exist." -- her user id on the Apache Jira is
> > dalyssakim.
> > >
> > > > >
> > >
> > > > > Thanks,
> > >
> > > > > Kirk
> > >
> > > > >
> > >
> > > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > --
> > >
> > > ~/William
> > >
> > >
> >
>



-- 
From:

Deepak D Dixit
deepakdixit2...@gmail.com
+919028507537

[jira] [Commented] (GEODE-2201) Make UITests more resilient

2016-12-11 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/GEODE-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15740920#comment-15740920
 ] 

ASF subversion and git services commented on GEODE-2201:


Commit d4276136337d2c9bee7336bafa281f2301af2a40 in geode's branch 
refs/heads/develop from [~jens.deppe]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=d427613 ]

GEODE-2201 Make UITests a bit more resilient

- Increase some timeouts
- Avoid StaleElementReferenceExceptions by retrying the element
  retrieval.


> Make UITests more resilient
> ---
>
> Key: GEODE-2201
> URL: https://issues.apache.org/jira/browse/GEODE-2201
> Project: Geode
>  Issue Type: Improvement
>  Components: pulse
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>
> The UITests are continually failing in CI. We need to make them great again.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (GEODE-2201) Make UITests more resilient

2016-12-11 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/GEODE-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15740921#comment-15740921
 ] 

ASF subversion and git services commented on GEODE-2201:


Commit df8730d9de9eb0a730cf1c61cf845748418747cb in geode's branch 
refs/heads/develop from [~jens.deppe]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=df8730d ]

Merge branch 'feature/GEODE-2201' into develop


> Make UITests more resilient
> ---
>
> Key: GEODE-2201
> URL: https://issues.apache.org/jira/browse/GEODE-2201
> Project: Geode
>  Issue Type: Improvement
>  Components: pulse
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>
> The UITests are continually failing in CI. We need to make them great again.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (GEODE-2201) Make UITests more resilient

2016-12-11 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/GEODE-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15740997#comment-15740997
 ] 

ASF subversion and git services commented on GEODE-2201:


Commit 0f8ef971b8f18bd144646e98468816df88d1d0c9 in geode's branch 
refs/heads/develop from [~jens.deppe]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=0f8ef97 ]

GEODE-2201 Spotless fix


> Make UITests more resilient
> ---
>
> Key: GEODE-2201
> URL: https://issues.apache.org/jira/browse/GEODE-2201
> Project: Geode
>  Issue Type: Improvement
>  Components: pulse
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>
> The UITests are continually failing in CI. We need to make them great again.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Fixed: apache/geode#1601 (develop - 0f8ef97)

2016-12-11 Thread Travis CI

Build Update for apache/geode
-

Build: #1601
Status: Fixed

Duration: 8 minutes and 59 seconds
Commit: 0f8ef97 (develop)
Author: Jens Deppe
Message: GEODE-2201 Spotless fix

View the changeset: 
https://github.com/apache/geode/compare/df8730d9de9e...0f8ef971b8f1

View the full build log and details: 
https://travis-ci.org/apache/geode/builds/183160053

--

You can configure recipients for build notifications in your .travis.yml file. 
See https://docs.travis-ci.com/user/notifications

[jira] [Resolved] (GEODE-1835) A message logged by the configure pdx command is incorrect

2016-12-11 Thread Amey Barve (JIRA)


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

Amey Barve resolved GEODE-1835.
---
Resolution: Fixed

This issue is resolved with https://github.com/apache/geode/pull/304 pull 
request.

> A message logged by the configure pdx command is incorrect
> --
>
> Key: GEODE-1835
> URL: https://issues.apache.org/jira/browse/GEODE-1835
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Barry Oglesby
>Assignee: Amey Barve
>
> The message below is only logged when there are no members. Instead, it 
> should be logged when there are members.
> {noformat}
> The command would only take effect on new data members joining the 
> distributed system. It won't affect the existing data members
> {noformat}
> The condition in {{PDXCommands.configurePDX}} is:
> {noformat}
> if (CliUtil.getAllNormalMembers(CliUtil.getCacheIfExists()).isEmpty()) {
>   ird.addLine(CliStrings.CONFIGURE_PDX__NORMAL__MEMBERS__WARNING);
> }
> {noformat}
> It should test for {{!isEmpty}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (GEODE-789) Create and clear define index shouldn't be available on disconnected GFSH

2016-12-11 Thread Amey Barve (JIRA)


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

Amey Barve reassigned GEODE-789:


Assignee: Amey Barve

> Create and clear define index shouldn't be available on disconnected GFSH
> -
>
> Key: GEODE-789
> URL: https://issues.apache.org/jira/browse/GEODE-789
> Project: Geode
>  Issue Type: Bug
>  Components: tools
>Reporter: William Markito Oliveira
>Assignee: Amey Barve
>
> The following gfsh commands for indexes shouldn't be available on a 
> disconnected gfsh session. 
> {code}
> gfsh>create defined indexes --
> Can't execute a remote command without connection. Use 'connect' first to 
> connect.
> gfsh>clear defined indexes
> Can't execute a remote command without connection. Use 'connect' first to 
> connect.
> gfsh>
> {code} 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (GEODE-1969) oplog closed while writing to oplog with gemfire.syncWrites=true

2016-12-11 Thread Amey Barve (JIRA)


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

Amey Barve reassigned GEODE-1969:
-

Assignee: Amey Barve

> oplog closed while writing to oplog with gemfire.syncWrites=true
> 
>
> Key: GEODE-1969
> URL: https://issues.apache.org/jira/browse/GEODE-1969
> Project: Geode
>  Issue Type: Bug
>  Components: persistence
>Reporter: Darrel Schneider
>Assignee: Amey Barve
>
> [info 2016/09/29 06:16:06.823 UTC  oplog#6> tid=0x19] OplogCompactor for nsxDiskStore compaction oplog id(s): 
> oplog#6
> [info 2016/09/29 06:16:08.232 UTC  oplog#6> tid=0x19] compaction did 6,310 creates and updates in 1,408 ms
> [info 2016/09/29 06:16:08.248 UTC  tid=0x19] Deleted 
> oplog#6 crf for disk store nsxDiskStore.
> [info 2016/09/29 06:16:08.256 UTC  tid=0x19] Deleted 
> oplog#6 krf for disk store nsxDiskStore.
> [info 2016/09/29 06:16:08.256 UTC  tid=0x19] Deleted 
> oplog#6 drf for disk store nsxDiskStore.
> [info 2016/09/29 06:17:03.887 UTC  GatewaySender_AsyncEventQueue_txLogEventQueue> tid=0x19] Created oplog#8 drf 
> for disk store nsxDiskStore.
> [info 2016/09/29 06:17:03.911 UTC  GatewaySender_AsyncEventQueue_txLogEventQueue> tid=0x19] Created oplog#8 crf 
> for disk store nsxDiskStore.
> [info 2016/09/29 06:17:04.031 UTC  tid=0x19] Created 
> oplog#7 krf for disk store nsxDiskStore.
> [info 2016/09/29 06:17:04.314 UTC  oplog#7> tid=0x19] OplogCompactor for nsxDiskStore compaction oplog id(s): 
> oplog#7
> [error 2016/09/29 06:17:16.075 UTC  oplog#7> tid=0x19] A DiskAccessException has occurred while writing to the 
> disk for disk store nsxDiskStore. The cache will be closed. 
> ?com.gemstone.gemfire.cache.DiskAccessException: For DiskStore: nsxDiskStore: 
> Failed writing key to "/common/nsxapi/data/self/BACKUPnsxDiskStore_7", caused 
> by java.io.IOException: Stream Closed ?at 
> com.gemstone.gemfire.internal.cache.Oplog.flushAll(Oplog.java:5235)
> [warn 2016/09/29 06:17:16.297 UTC  GatewaySender_AsyncEventQueue_txLogEventQueue> tid=0x19] 
> com.gemstone.gemfire.internal.cache.wan.GatewaySenderEventCallbackDispatcher@55bded67:
>  Exception during processing batch 448
> com.gemstone.gemfire.internal.cache.wan.GatewaySenderException: 
> com.gemstone.gemfire.internal.cache.wan.GatewaySenderEventCallbackDispatcher@55bded67:
>  Exception during processing batch 448, caused by 
> com.gemstone.gemfire.cache.CacheClosedException: For DiskStore: nsxDiskStore: 
> Failed writing key to "/common/nsxapi/data/self/BACKUPnsxDiskStore_7", caused 
> by com.gemstone.gemfire.cache.DiskAccessException: For DiskStore: 
> nsxDiskStore: Failed writing key to 
> "/common/nsxapi/data/self/BACKUPnsxDiskStore_7", caused by 
> java.io.IOException: Stream Closed
> at 
> com.gemstone.gemfire.internal.cache.wan.GatewaySenderEventCallbackDispatcher.dispatchBatch(GatewaySenderEventCallbackDispatcher.java:173)
> at 
> com.gemstone.gemfire.internal.cache.wan.GatewaySenderEventCallbackDispatcher.dispatchBatch(GatewaySenderEventCallbackDispatcher.java:83)
> at 
> com.gemstone.gemfire.internal.cache.wan.AbstractGatewaySenderEventProcessor.processQueue(AbstractGatewaySenderEventProcessor.java:579)
> at 
> com.gemstone.gemfire.internal.cache.wan.serial.SerialGatewaySenderEventProcessor.run(SerialGatewaySenderEventProcessor.java:219)
> Caused by: com.gemstone.gemfire.cache.CacheClosedException: For DiskStore: 
> nsxDiskStore: Failed writing key to 
> "/common/nsxapi/data/self/BACKUPnsxDiskStore_7", caused by 
> com.gemstone.gemfire.cache.DiskAccessException: For DiskStore: nsxDiskStore: 
> Failed writing key to "/common/nsxapi/data/self/BACKUPnsxDiskStore_7", caused 
> by java.io.IOException: Stream Closed
> at 
> com.gemstone.gemfire.internal.cache.GemFireCacheImpl$Stopper.generateCancelledException(GemFireCacheImpl.java:1299)
> at 
> com.gemstone.gemfire.CancelCriterion.checkCancelInProgress(CancelCriterion.java:82)
> at 
> com.gemstone.gemfire.internal.cache.TXManagerImpl.checkClosed(TXManagerImpl.java:606)
> at 
> com.gemstone.gemfire.internal.cache.TXManagerImpl.begin(TXManagerImpl.java:279)
> at 
> com.vmware.nsx.management.container.dao.gemfire.GemFireTxLogDao.processTxLog(GemFireTxLogDao.java:119)
> at 
> com.vmware.nsx.management.container.dao.gemfire.TxLogAsyncEventListener.processEvents(TxLogAsyncEventListener.java:93)
> at 
> com.gemstone.gemfire.internal.cache.wan.GatewaySenderEventCallbackDispatcher.dispatchBatch(GatewaySenderEventCallbackDispatcher.java:164)
> ... 3 more
> Caused by: com.gemstone.gemfire.cache.DiskAccessException: For DiskStore: 
> nsxDiskStore: Failed writing key to 
> "/common/nsxapi/data/self/BACKUPnsxDiskStore_7", caused by 
> java.io.IOException: Stream Closed
>

[jira] [Updated] (GEODE-789) Create and clear define index shouldn't be available on disconnected GFSH

2016-12-11 Thread Amey Barve (JIRA)


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

Amey Barve updated GEODE-789:
-
Component/s: gfsh

> Create and clear define index shouldn't be available on disconnected GFSH
> -
>
> Key: GEODE-789
> URL: https://issues.apache.org/jira/browse/GEODE-789
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh, tools
>Reporter: William Markito Oliveira
>Assignee: Amey Barve
>
> The following gfsh commands for indexes shouldn't be available on a 
> disconnected gfsh session. 
> {code}
> gfsh>create defined indexes --
> Can't execute a remote command without connection. Use 'connect' first to 
> connect.
> gfsh>clear defined indexes
> Can't execute a remote command without connection. Use 'connect' first to 
> connect.
> gfsh>
> {code} 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (GEODE-1541) statsListUniqueId should be an AtomicLong

2016-12-11 Thread Amey Barve (JIRA)


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

Amey Barve reassigned GEODE-1541:
-

Assignee: Amey Barve

> statsListUniqueId should be an AtomicLong
> -
>
> Key: GEODE-1541
> URL: https://issues.apache.org/jira/browse/GEODE-1541
> Project: Geode
>  Issue Type: Improvement
>  Components: statistics
>Reporter: Darrel Schneider
>Assignee: Amey Barve
>
> In InternalDistributedSystem the following instance variables:
>   private long statsListUniqueId = 1;
>   private final Object statsListUniqueIdLock = new Object();
> should be changed to an AtomicLong.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Assigning Jira tickets to new contributors

2016-12-11 Thread Kai Jiang

Thanks William :)

Best,
Kai.

On Sun, Dec 11, 2016 at 8:08 PM, Deepak Dixit 
wrote:

> Thanks William :)
> I am able to assign JIRA on my apache id.
>
>
> On Mon, Dec 12, 2016 at 8:29 AM, William Markito Oliveira <
> william.mark...@gmail.com> wrote:
>
> > Great! So assigning people to the "contributors" role is good enough for
> > this, glad it worked!
> >
> > On Sun, Dec 11, 2016 at 6:51 PM Kirk Lund  wrote:
> >
> > > Thanks William!
> > >
> > > On Sun, Dec 11, 2016 at 6:30 PM William Markito Oliveira <
> > > william.mark...@gmail.com> wrote:
> > >
> > > > I've just add all 3 (vectorijk, deepakddixit, dalyssakim) as
> > > "contributors"
> > > >
> > > > to the Geode JIRA project, but in the past we had problems with
> people
> > > not
> > > >
> > > > being able to "self-assign" JIRAs if they're not in the "committers"
> > > group.
> > > >
> > > >
> > > >
> > > > The workaround was to include them into the committers group on JIRA,
> > > which
> > > >
> > > > don't necessary give them commit privilege on the codebase, just on
> > JIRA.
> > > >
> > > > Alternatively now that we graduated we could try fixing the role
> > > >
> > > > "contributor" of JIRA to at least allow people to assign JIRAs to
> > > >
> > > > themselves.
> > > >
> > > >
> > > >
> > > > Please give it a try now and see if you can assign the tickets to
> you,
> > > >
> > > > otherwise let us know.   Thanks!
> > > >
> > > >
> > > >
> > > > On Sun, Dec 11, 2016 at 5:35 AM, Kai Jiang 
> wrote:
> > > >
> > > >
> > > >
> > > > > Hi Kirk,
> > > >
> > > > >
> > > >
> > > > > I am also a new contributor to GEODE project. Also, I am working
> on a
> > > few
> > > >
> > > > > issues(GEODE-2172  jira/browse/GEODE-2172>
> > > >
> > > > > GEODE-2167 
> > > GEODE-224
> > > >
> > > > > ) . Maybe these
> > issue
> > > >
> > > > > could be assigned to me.
> > > >
> > > > > Meanwhile, I will be appreciated if someone could review my pull
> > > > requests.
> > > >
> > > > >
> > > >
> > > > > JIRA id: vectorijk
> > > >
> > > > > Github id: vectorijk
> > > >
> > > > >
> > > >
> > > > > Thanks,
> > > >
> > > > > Kai.
> > > >
> > > > >
> > > >
> > > > >
> > > >
> > > > >
> > > >
> > > > > On Sat, Dec 10, 2016 at 10:57 PM, Deepak Dixit <
> > > > deepakdixit2...@gmail.com>
> > > >
> > > > > wrote:
> > > >
> > > > >
> > > >
> > > > > > Hello Kirk,
> > > >
> > > > > >
> > > >
> > > > > > I remember some apache help document mentioning need for user to
> be
> > > > added
> > > >
> > > > > > to the project group.
> > > >
> > > > > > May be adding user to GEODE project group will help in enabling
> > them
> > > to
> > > >
> > > > > > assign issues to themselves.
> > > >
> > > > > >
> > > >
> > > > > > Can you please grant similar permission to me (details are added
> > > below)
> > > >
> > > > > so
> > > >
> > > > > > I can assign JIRA issue I am working on?
> > > >
> > > > > > I am currently working on GEODE-2109 and just finished with
> > > GEODE-734.
> > > >
> > > > > >
> > > >
> > > > > > Detail for apache id
> > > >
> > > > > > Email ID: deepakdixit2...@gmail.com
> > > >
> > > > > > apache id: deepakddixit
> > > >
> > > > > >
> > > >
> > > > > > Thanks,
> > > >
> > > > > >
> > > >
> > > > > > Deepak
> > > >
> > > > > >
> > > >
> > > > > >
> > > >
> > > > > > On Dec 11, 2016 9:41 AM, "Kirk Lund"  wrote:
> > > >
> > > > > >
> > > >
> > > > > > Does anyone know what needs to be done to enable assigning a Jira
> > > > ticket
> > > >
> > > > > to
> > > >
> > > > > > a new contributor? Alyssa Kim filed GEODE-2203 and would like to
> > have
> > > > the
> > > >
> > > > > > ticket assigned to her but Jira shows either "No Matches" or
> "User
> > > >
> > > > > 'Alyssa
> > > >
> > > > > > Kim' does not exist." -- her user id on the Apache Jira is
> > > dalyssakim.
> > > >
> > > > > >
> > > >
> > > > > > Thanks,
> > > >
> > > > > > Kirk
> > > >
> > > > > >
> > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > >
> > > > ~/William
> > > >
> > > >
> > >
> >
>
>
>
> --
> From:
>
> Deepak D Dixit
> deepakdixit2...@gmail.com
> +919028507537
>

[jira] [Assigned] (GEODE-224) Geode Spark connector parser is not processing type casting properly

2016-12-11 Thread Kai Jiang (JIRA)


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

Kai Jiang reassigned GEODE-224:
---

Assignee: Kai Jiang

> Geode Spark connector parser is not processing type casting properly
> 
>
> Key: GEODE-224
> URL: https://issues.apache.org/jira/browse/GEODE-224
> Project: Geode
>  Issue Type: Bug
>  Components: extensions
>Reporter: William Markito Oliveira
>Assignee: Kai Jiang
>Priority: Minor
>  Labels: gsoc2016
>
> Using GFSH a user can execute queries casting the data types but that's not 
> working using the geode-spark-connector. 
> {code}
> scala> sqlContext.gemfireOQL("SELECT (Double)t.ema, (Double)t.future_ema, 
> (Double)t.close, t.entryTimestamp FROM /TechIndicators t ");
> java.lang.RuntimeException: No result when parsing failed
> at scala.sys.package$.error(package.scala:27)
> at scala.util.parsing.combinator.Parsers$NoSuccess.get(Parsers.scala:181)
> at scala.util.parsing.combinator.Parsers$NoSuccess.get(Parsers.scala:167)
> at 
> io.pivotal.gemfire.spark.connector.internal.oql.QueryRDD.getRegionPathFromQuery(QueryRDD.scala:56)
> at 
> io.pivotal.gemfire.spark.connector.internal.oql.QueryRDD.getPartitions(QueryRDD.scala:24)
> at org.apache.spark.rdd.RDD$$anonfun$partitions$2.apply(RDD.scala:219)
> at org.apache.spark.rdd.RDD$$anonfun$partitions$2.apply(RDD.scala:217)
> at scala.Option.getOrElse(Option.scala:120)
> at org.apache.spark.rdd.RDD.partitions(RDD.scala:217)
> at org.apache.spark.rdd.RDD.take(RDD.scala:1156)
> at org.apache.spark.rdd.RDD.first(RDD.scala:1189)
> at 
> io.pivotal.gemfire.spark.connector.internal.oql.SchemaBuilder.toSparkSchema(SchemaBuilder.scala:30)
> at 
> io.pivotal.gemfire.spark.connector.internal.oql.OQLRelation.schema(RDDConverter.scala:13)
> at 
> org.apache.spark.sql.sources.LogicalRelation.(LogicalRelation.scala:30)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (GEODE-224) Geode Spark connector parser is not processing type casting properly

2016-12-11 Thread Kai Jiang (JIRA)


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

Kai Jiang updated GEODE-224:

Fix Version/s: 1.1.0

> Geode Spark connector parser is not processing type casting properly
> 
>
> Key: GEODE-224
> URL: https://issues.apache.org/jira/browse/GEODE-224
> Project: Geode
>  Issue Type: Bug
>  Components: extensions
>Reporter: William Markito Oliveira
>Assignee: Kai Jiang
>Priority: Minor
>  Labels: gsoc2016
> Fix For: 1.1.0
>
>
> Using GFSH a user can execute queries casting the data types but that's not 
> working using the geode-spark-connector. 
> {code}
> scala> sqlContext.gemfireOQL("SELECT (Double)t.ema, (Double)t.future_ema, 
> (Double)t.close, t.entryTimestamp FROM /TechIndicators t ");
> java.lang.RuntimeException: No result when parsing failed
> at scala.sys.package$.error(package.scala:27)
> at scala.util.parsing.combinator.Parsers$NoSuccess.get(Parsers.scala:181)
> at scala.util.parsing.combinator.Parsers$NoSuccess.get(Parsers.scala:167)
> at 
> io.pivotal.gemfire.spark.connector.internal.oql.QueryRDD.getRegionPathFromQuery(QueryRDD.scala:56)
> at 
> io.pivotal.gemfire.spark.connector.internal.oql.QueryRDD.getPartitions(QueryRDD.scala:24)
> at org.apache.spark.rdd.RDD$$anonfun$partitions$2.apply(RDD.scala:219)
> at org.apache.spark.rdd.RDD$$anonfun$partitions$2.apply(RDD.scala:217)
> at scala.Option.getOrElse(Option.scala:120)
> at org.apache.spark.rdd.RDD.partitions(RDD.scala:217)
> at org.apache.spark.rdd.RDD.take(RDD.scala:1156)
> at org.apache.spark.rdd.RDD.first(RDD.scala:1189)
> at 
> io.pivotal.gemfire.spark.connector.internal.oql.SchemaBuilder.toSparkSchema(SchemaBuilder.scala:30)
> at 
> io.pivotal.gemfire.spark.connector.internal.oql.OQLRelation.schema(RDDConverter.scala:13)
> at 
> org.apache.spark.sql.sources.LogicalRelation.(LogicalRelation.scala:30)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Assigning Jira tickets to new contributors

Build failed in Jenkins: Geode-nightly #681

[jira] [Assigned] (GEODE-2061) Remove PdxInstanceInputStream

Re: Build failed in Jenkins: Geode-nightly #680

Re: Build failed in Jenkins: Geode-nightly #680

[jira] [Commented] (GEODE-2203) gfsh status locator/server - Give more descriptive output on empty parameter

[jira] [Commented] (GEODE-2203) gfsh status locator/server - Give more descriptive output on empty parameter

[jira] [Updated] (GEODE-2172) CustomConfigWithCacheIntegrationTest fails with AssertionError on Windows

Re: Assigning Jira tickets to new contributors

[jira] [Assigned] (GEODE-2203) gfsh status locator/server - Give more descriptive output on empty parameter

Re: Assigning Jira tickets to new contributors

Re: Assigning Jira tickets to new contributors

Re: Assigning Jira tickets to new contributors

[jira] [Assigned] (GEODE-2109) calling submit on ExecutionService can cause exceptions to be lost

Re: Assigning Jira tickets to new contributors

[jira] [Commented] (GEODE-2201) Make UITests more resilient

[jira] [Commented] (GEODE-2201) Make UITests more resilient

[jira] [Commented] (GEODE-2201) Make UITests more resilient

Fixed: apache/geode#1601 (develop - 0f8ef97)

[jira] [Resolved] (GEODE-1835) A message logged by the configure pdx command is incorrect

[jira] [Assigned] (GEODE-789) Create and clear define index shouldn't be available on disconnected GFSH

[jira] [Assigned] (GEODE-1969) oplog closed while writing to oplog with gemfire.syncWrites=true

[jira] [Updated] (GEODE-789) Create and clear define index shouldn't be available on disconnected GFSH

[jira] [Assigned] (GEODE-1541) statsListUniqueId should be an AtomicLong

Re: Assigning Jira tickets to new contributors

[jira] [Assigned] (GEODE-224) Geode Spark connector parser is not processing type casting properly

[jira] [Updated] (GEODE-224) Geode Spark connector parser is not processing type casting properly

27 matches

Site Navigation

Mail list logo

Footer information