[GitHub] geode issue #540: GEODE-2950: Updated error messages

Github user DivineEnder commented on the issue: https://github.com/apache/geode/pull/540 @ladyVader @nabarunnag @boglesby @jhuynh1 @upthewaterspout @gesterzhou --- 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

[GitHub] geode pull request #540: GEODE-2950: Updated error messages

GitHub user DivineEnder opened a pull request: https://github.com/apache/geode/pull/540 GEODE-2950: Updated error messages * Different error messages are displayed when validating region names versus indexes. * Added flexible enum allowing for expanded error messages

[jira] [Updated] (GEODE-2993) Lucene query inconsistency detected after user region event fired during cache close

[ https://issues.apache.org/jira/browse/GEODE-2993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey updated GEODE-2993: --- Affects Version/s: 1.2.0 > Lucene query inconsistency detected after

[jira] [Commented] (GEODE-2957) null used as a default parameter when specifying analyzers

[ https://issues.apache.org/jira/browse/GEODE-2957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025572#comment-16025572 ] ASF GitHub Bot commented on GEODE-2957: --- Github user asfgit closed the pull request at:

[jira] [Commented] (GEODE-2939) Initiate bucket event tracker and get GII from different source could lead to bucket copies inconsistence

[ https://issues.apache.org/jira/browse/GEODE-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025585#comment-16025585 ] ASF subversion and git services commented on GEODE-2939: Commit

[jira] [Created] (GEODE-2998) New flow: remove/removeAll

Brian Baynes created GEODE-2998: --- Summary: New flow: remove/removeAll Key: GEODE-2998 URL: https://issues.apache.org/jira/browse/GEODE-2998 Project: Geode Issue Type: Sub-task

[jira] [Updated] (GEODE-2996) New flow: put/putAll

[ https://issues.apache.org/jira/browse/GEODE-2996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Baynes updated GEODE-2996: Description: Create proto message definitions and op handler for put/putAll messages. Client

[jira] [Created] (GEODE-2999) New flow: replace/put if absent

Brian Baynes created GEODE-2999: --- Summary: New flow: replace/put if absent Key: GEODE-2999 URL: https://issues.apache.org/jira/browse/GEODE-2999 Project: Geode Issue Type: Sub-task

[jira] [Created] (GEODE-2995) Introduce new protocol flow into core

Brian Baynes created GEODE-2995: --- Summary: Introduce new protocol flow into core Key: GEODE-2995 URL: https://issues.apache.org/jira/browse/GEODE-2995 Project: Geode Issue Type: Sub-task

[jira] [Created] (GEODE-2997) New flow: putAll/getAll

Brian Baynes created GEODE-2997: --- Summary: New flow: putAll/getAll Key: GEODE-2997 URL: https://issues.apache.org/jira/browse/GEODE-2997 Project: Geode Issue Type: Sub-task

[jira] [Created] (GEODE-2996) New flow: put/get

Brian Baynes created GEODE-2996: --- Summary: New flow: put/get Key: GEODE-2996 URL: https://issues.apache.org/jira/browse/GEODE-2996 Project: Geode Issue Type: Sub-task Components:

[jira] [Updated] (GEODE-2996) New flow: put/get

[ https://issues.apache.org/jira/browse/GEODE-2996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Baynes updated GEODE-2996: Description: Create proto message definitions and op handler for put/get messages. Client should

[jira] [Updated] (GEODE-2997) New flow: putAll/getAll

[ https://issues.apache.org/jira/browse/GEODE-2997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Baynes updated GEODE-2997: Description: Create proto message definitions and op handler for putAll/getAll messages. Client

[jira] [Resolved] (GEODE-2985) Doc task: making/using backups when there are indexes

[ https://issues.apache.org/jira/browse/GEODE-2985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller resolved GEODE-2985. Resolution: Invalid Ticket has incorrect info. Will open a new ticket with correct

[GitHub] geode pull request #537: GEODE-2957: Added DEFAULT as a standardAnalyzer key...

Github user asfgit closed the pull request at: https://github.com/apache/geode/pull/537 --- 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

[jira] [Commented] (GEODE-2957) null used as a default parameter when specifying analyzers

[ https://issues.apache.org/jira/browse/GEODE-2957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025571#comment-16025571 ] ASF subversion and git services commented on GEODE-2957: Commit

[jira] [Resolved] (GEODE-2939) Initiate bucket event tracker and get GII from different source could lead to bucket copies inconsistence

[ https://issues.apache.org/jira/browse/GEODE-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-2939. - Resolution: Fixed Fix Version/s: 1.2.0 > Initiate bucket event tracker and get GII from different

[jira] [Updated] (GEODE-2997) New flow: get/getAll

[ https://issues.apache.org/jira/browse/GEODE-2997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Baynes updated GEODE-2997: Description: Create proto message definitions and op handler for get/getAll messages. Client

[jira] [Commented] (GEODE-2944) lucene queries on String values (vs. objects) requires obscure/undocumented defaultField (__REGION_VALUE_FIELD)

[ https://issues.apache.org/jira/browse/GEODE-2944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025334#comment-16025334 ] ASF subversion and git services commented on GEODE-2944: Commit

[GitHub] geode pull request #533: GEODE-2944: Added __REGION_VALUE_FIELD explanation ...

Github user asfgit closed the pull request at: https://github.com/apache/geode/pull/533 --- 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

[jira] [Commented] (GEODE-2944) lucene queries on String values (vs. objects) requires obscure/undocumented defaultField (__REGION_VALUE_FIELD)

[ https://issues.apache.org/jira/browse/GEODE-2944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025335#comment-16025335 ] ASF GitHub Bot commented on GEODE-2944: --- Github user asfgit closed the pull request at:

[jira] [Commented] (GEODE-2950) Lucene index names should be restricted to valid region names since the index name becomes part of a region

[ https://issues.apache.org/jira/browse/GEODE-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025481#comment-16025481 ] ASF GitHub Bot commented on GEODE-2950: --- GitHub user DivineEnder opened a pull request:

[jira] [Commented] (GEODE-2950) Lucene index names should be restricted to valid region names since the index name becomes part of a region

[ https://issues.apache.org/jira/browse/GEODE-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025482#comment-16025482 ] ASF GitHub Bot commented on GEODE-2950: --- Github user DivineEnder commented on the issue:

[jira] [Commented] (GEODE-2993) Lucene query inconsistency detected after user region event fired during cache close

[ https://issues.apache.org/jira/browse/GEODE-2993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025508#comment-16025508 ] ASF subversion and git services commented on GEODE-2993: Commit

[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #565 was SUCCESSFUL (with 1848 tests)

--- Spring Data GemFire > Nightly-ApacheGeode > #565 was successful. --- Scheduled 1850 tests in total. https://build.spring.io/browse/SGF-NAG-565/ -- This

[GitHub] geode pull request #540: GEODE-2950: Updated error messages

Github user asfgit closed the pull request at: https://github.com/apache/geode/pull/540 --- 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

[jira] [Commented] (GEODE-2950) Lucene index names should be restricted to valid region names since the index name becomes part of a region

[ https://issues.apache.org/jira/browse/GEODE-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025541#comment-16025541 ] ASF GitHub Bot commented on GEODE-2950: --- Github user asfgit closed the pull request at:

[jira] [Commented] (GEODE-2950) Lucene index names should be restricted to valid region names since the index name becomes part of a region

[ https://issues.apache.org/jira/browse/GEODE-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025540#comment-16025540 ] ASF subversion and git services commented on GEODE-2950: Commit

[jira] [Commented] (GEODE-2818) add alias to any command's options that involves "group", "member", "jar"

[ https://issues.apache.org/jira/browse/GEODE-2818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025538#comment-16025538 ] ASF GitHub Bot commented on GEODE-2818: --- Github user jaredjstewart commented on the issue:

[GitHub] geode issue #539: GEODE-2818: add alias to any command's options that involv...

Github user jaredjstewart commented on the issue: https://github.com/apache/geode/pull/539 Thanks for your contribution, Emily! It looks like this branch will need to be rebased onto the latest develop to apply cleanly. Would you mind updating the PR with a rebased version of these

[jira] [Commented] (GEODE-2941) Pulse documentation is outdated

[ https://issues.apache.org/jira/browse/GEODE-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025348#comment-16025348 ] ASF subversion and git services commented on GEODE-2941: Commit

Re: Review Request 59404: GEODE-2939: make sure event tracker is initiated from the GII provider

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/59404/#review176146 ---

[jira] [Resolved] (GEODE-2944) lucene queries on String values (vs. objects) requires obscure/undocumented defaultField (__REGION_VALUE_FIELD)

[ https://issues.apache.org/jira/browse/GEODE-2944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Anuta resolved GEODE-2944. Resolution: Fixed Fix Version/s: 1.2.0 > lucene queries on String values (vs. objects)

Re: Proposal: Remove the "user-command-packages" system property

What JVM does this scanning? Is it just the top-level shell JVM or does it happen on the jmx-manager side? On Thu, May 25, 2017 at 1:01 PM, Jared Stewart wrote: > It sounds like we're on the same page. > > The current behavior requires two pieces from a user who wants to

Re: Proposal: Remove the "user-command-packages" system property

both sides. On Thu, May 25, 2017 at 2:16 PM, Darrel Schneider wrote: > What JVM does this scanning? Is it just the top-level shell JVM or does it > happen on the jmx-manager side? > > On Thu, May 25, 2017 at 1:01 PM, Jared Stewart > wrote: > > > It

[GitHub] geode issue #539: GEODE-2818: add alias to any command's options that involv...

Github user YehEmily commented on the issue: https://github.com/apache/geode/pull/539 Precheckin pending! --- 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,

[jira] [Commented] (GEODE-2818) add alias to any command's options that involves "group", "member", "jar"

[ https://issues.apache.org/jira/browse/GEODE-2818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025358#comment-16025358 ] ASF GitHub Bot commented on GEODE-2818: --- Github user YehEmily commented on the issue:

[jira] [Commented] (GEODE-2818) add alias to any command's options that involves "group", "member", "jar"

[ https://issues.apache.org/jira/browse/GEODE-2818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025357#comment-16025357 ] ASF GitHub Bot commented on GEODE-2818: --- GitHub user YehEmily opened a pull request:

[GitHub] geode pull request #539: GEODE-2818: add alias to any command's options that...

GitHub user YehEmily opened a pull request: https://github.com/apache/geode/pull/539 GEODE-2818: add alias to any command's options that involves "group", "member", "jar" Thank you for submitting a contribution to Apache Geode. In order to streamline the review of the

[GitHub] geode issue #538: GEODE-2975: Change the location of the lucene xsd

Github user boglesby commented on the issue: https://github.com/apache/geode/pull/538 This looks good for these xmls: ``` ``` ``` ``` it still throws a ClassCastException for this, though: ``` ``` I'm not sure if thats a problem or if its

[jira] [Commented] (GEODE-2975) Attributes are not validated in lucene xml configuration

[ https://issues.apache.org/jira/browse/GEODE-2975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025385#comment-16025385 ] ASF GitHub Bot commented on GEODE-2975: --- Github user boglesby commented on the issue:

[jira] [Updated] (GEODE-2990) fix testXmlCacheCreationWithPools

[ https://issues.apache.org/jira/browse/GEODE-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Burghardt updated GEODE-2990: Component/s: native client > fix testXmlCacheCreationWithPools >

[jira] [Created] (GEODE-2992) Update openssl download URI

Ernest Burghardt created GEODE-2992: --- Summary: Update openssl download URI Key: GEODE-2992 URL: https://issues.apache.org/jira/browse/GEODE-2992 Project: Geode Issue Type: Bug

[jira] [Commented] (GEODE-2992) Update openssl download URI

[ https://issues.apache.org/jira/browse/GEODE-2992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025442#comment-16025442 ] ASF subversion and git services commented on GEODE-2992: Commit

[GitHub] geode pull request #536: GEODE-2977: make group/name option values consisten...

Github user asfgit closed the pull request at: https://github.com/apache/geode/pull/536 --- 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

[jira] [Commented] (GEODE-2977) commands should take string[] as the value for --group and --memberId(--name) whenever possible

[ https://issues.apache.org/jira/browse/GEODE-2977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025460#comment-16025460 ] ASF subversion and git services commented on GEODE-2977: Commit

[jira] [Created] (GEODE-2993) Lucene query inconsistency detected after user region event fired during cache close

Shelley Lynn Hughes-Godfrey created GEODE-2993: -- Summary: Lucene query inconsistency detected after user region event fired during cache close Key: GEODE-2993 URL:

Re: Proposal: Remove the "user-command-packages" system property

The only concern I would have is that this might cause gfsh to load other things that implement the spring CommandMarker that have nothing to do with gfsh simply because they are in one of the jars. I really don't know how likely that would be to happen but it seems more likely since the scan

[jira] [Assigned] (GEODE-2993) Lucene query inconsistency detected after user region event fired during cache close

[ https://issues.apache.org/jira/browse/GEODE-2993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey reassigned GEODE-2993: -- Assignee: Shelley Lynn Hughes-Godfrey > Lucene query

[jira] [Updated] (GEODE-2975) Attributes are not validated in lucene xml configuration

[ https://issues.apache.org/jira/browse/GEODE-2975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joey McAllister updated GEODE-2975: --- Component/s: docs > Attributes are not validated in lucene xml configuration >

[jira] [Commented] (GEODE-2975) Attributes are not validated in lucene xml configuration

[ https://issues.apache.org/jira/browse/GEODE-2975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025325#comment-16025325 ] ASF GitHub Bot commented on GEODE-2975: --- Github user upthewaterspout commented on the issue:

[GitHub] geode issue #538: GEODE-2975: Change the location of the lucene xsd

Github user upthewaterspout commented on the issue: https://github.com/apache/geode/pull/538 @metatype - Yes, we'll need to update the website as well, the location of the xsd is also wrong on the website, but for different reasons. --- If your project is set up for it, you can

[jira] [Created] (GEODE-2991) "destroy gateway-sender" command not in documentation

Emily Yeh created GEODE-2991: Summary: "destroy gateway-sender" command not in documentation Key: GEODE-2991 URL: https://issues.apache.org/jira/browse/GEODE-2991 Project: Geode Issue Type: Bug

[jira] [Commented] (GEODE-2977) commands should take string[] as the value for --group and --memberId(--name) whenever possible

[ https://issues.apache.org/jira/browse/GEODE-2977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025462#comment-16025462 ] ASF GitHub Bot commented on GEODE-2977: --- Github user asfgit closed the pull request at:

Re: Review Request 59542: GEODE-2974: rename ResultBuilder methods: GemFire -> Geode

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/59542/#review176144 --- - Darrel Schneider On May 24, 2017, 3:20 p.m., Ken Howe wrote:

Re: Review Request 59546: GEODE-2940 Remove verification of locator host on start

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/59546/#review176020 --- Good work! I have a few minor comments and a couple of things I'm

Re: Review Request 59546: GEODE-2940 Remove verification of locator host on start

> On May 25, 2017, 5:51 p.m., Galen O'Sullivan wrote: > > geode-core/src/test/java/org/apache/geode/distributed/internal/DistributionConfigJUnitTest.java > > Lines 346 (patched) > > > > > > Could this be split into

[jira] [Created] (GEODE-2988) create a security example

Swapnil Bawaskar created GEODE-2988: --- Summary: create a security example Key: GEODE-2988 URL: https://issues.apache.org/jira/browse/GEODE-2988 Project: Geode Issue Type: Sub-task

[jira] [Created] (GEODE-2989) Improve mechanism for scanning the classpath to find gfsh commands

Jared Stewart created GEODE-2989: Summary: Improve mechanism for scanning the classpath to find gfsh commands Key: GEODE-2989 URL: https://issues.apache.org/jira/browse/GEODE-2989 Project: Geode

[jira] [Assigned] (GEODE-2989) Improve mechanism for scanning the classpath to find gfsh commands

[ https://issues.apache.org/jira/browse/GEODE-2989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jared Stewart reassigned GEODE-2989: Assignee: Jared Stewart > Improve mechanism for scanning the classpath to find gfsh

[GitHub] geode pull request #532: GEODE-2950: Adding validation checks on create Luce...

Github user asfgit closed the pull request at: https://github.com/apache/geode/pull/532 --- 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

[jira] [Commented] (GEODE-2950) Lucene index names should be restricted to valid region names since the index name becomes part of a region

[ https://issues.apache.org/jira/browse/GEODE-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025158#comment-16025158 ] ASF subversion and git services commented on GEODE-2950: Commit

[jira] [Created] (GEODE-2990) fix testXmlCacheCreationWithPools

Ernest Burghardt created GEODE-2990: --- Summary: fix testXmlCacheCreationWithPools Key: GEODE-2990 URL: https://issues.apache.org/jira/browse/GEODE-2990 Project: Geode Issue Type: Bug

[jira] [Updated] (GEODE-2988) create a security example

[ https://issues.apache.org/jira/browse/GEODE-2988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joey McAllister updated GEODE-2988: --- Component/s: docs > create a security example > - > >

[jira] [Commented] (GEODE-2950) Lucene index names should be restricted to valid region names since the index name becomes part of a region

[ https://issues.apache.org/jira/browse/GEODE-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025159#comment-16025159 ] ASF GitHub Bot commented on GEODE-2950: --- Github user asfgit closed the pull request at:

Re: What to do with Singletons

> On May 25, 2017, at 7:55 AM, Udo Kohlmeyer wrote: > > @Kirk, I think your approach to reduce the number of singleton access is > good. I agree and believe that any operational invocation (Function,Command, > DistributionMessage,etc...) should provide a mechanism to be

Re: What to do with the geode-spark-connector

+1 for A > On 24 May, 2017, at 21:30, Jared Stewart wrote: > > +1 for A > > On May 24, 2017 6:48 PM, "Kirk Lund" wrote: > >> +1 for A >> >> On Wed, May 24, 2017 at 5:50 PM, Jianxia Chen wrote: >> >>> I prefer option A: Move it into

Re: Review Request 59562: GEODE-2941 Pulse documentation is outdated

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/59562/#review176079 --- Ship it! Ship It! - Joey McAllister On May 25, 2017, 12:45

Re: What to do with the geode-spark-connector

+1 to moving it from develop to it's own repo and gradle build. The spark-connector is another quintessential project that should be treated as an external module to geode. On 5/25/17 07:58, Anthony Baker wrote: I agree with Anil that the spark-connector is woefully behind. The spark

Re: What to do with the geode-spark-connector

+1 On Thu, May 25, 2017 at 8:15 AM, Udo Kohlmeyer wrote: > +1 to moving it from develop to it's own repo and gradle build. The > spark-connector is another quintessential project that should be treated as > an external module to geode. > > > On 5/25/17 07:58, Anthony Baker

Re: What to do with the geode-spark-connector

+1 on A On Thu, May 25, 2017 at 8:21 AM, Michael William Dodge wrote: > +1 for A > > > On 24 May, 2017, at 21:30, Jared Stewart wrote: > > > > +1 for A > > > > On May 24, 2017 6:48 PM, "Kirk Lund" wrote: > > > >> +1 for A > >> > >> On

Re: What to do with the geode-spark-connector

I have similar thoughts as Anthony on this issue. No matter if it is a separate repo or branch I think it will be left behind. I think the bigger question is does this community want to continue to support the connector? --Mark On Thu, May 25, 2017 at 8:34 AM Ernest Burghardt

Re: Review Request 59542: GEODE-2974: rename ResultBuilder methods: GemFire -> Geode

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/59542/#review176087 --- Ship it! Ship It! - Patrick Rhomberg On May 24, 2017, 10:20

Re: What to do with Singletons

@Kirk, I think your approach to reduce the number of singleton access is good. I agree and believe that any operational invocation (Function,Command, DistributionMessage,etc...) should provide a mechanism to be able to access all relevant all contextual information required to execute the task

Re: What to do with the geode-spark-connector

I agree with Anil that the spark-connector is woefully behind. The spark community is moving fast and the connector is based on a 2yo release. That code hasn’t seen much activity outside of rebranding. If we split it out into a different repo it just moves the problem—is anyone volunteering

Re: Geode Nightly build is consistently RED

This is topic is very relevant given that we are working towards a 1.2.0 release. In order to release we need—at the very minimum--a clean pass through distributedTest. Recently we’ve had some instability that has contributed to failing tests. Anthony > On May 24, 2017, at 4:54 PM, Kirk

RE: Geode Exception: cluster configuration service not available

Hi Aravind, Why did you miss the locator property --enable-cluster-configuration=true \ ? Anton Mironenko Software Architect Amdocs ASP team -Original Message- From: Aravind Musigumpula Sent: Thursday, May 25, 2017 10:54 To: dev@geode.apache.org Subject: RE: Geode Exception: cluster

[jira] [Commented] (GEODE-2954) Old client gets null memberID in cache listener

[ https://issues.apache.org/jira/browse/GEODE-2954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16024807#comment-16024807 ] ASF subversion and git services commented on GEODE-2954: Commit

[jira] [Resolved] (GEODE-2955) gfsh create lucene index command should validate the region name parameter

[ https://issues.apache.org/jira/browse/GEODE-2955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Anuta resolved GEODE-2955. Resolution: Fixed Fix Version/s: 1.2.0 > gfsh create lucene index command should validate

Re: What to do with Singletons

> > But we should probably create another thread to talk about it to keep this > one focused on the singletons discussion. > +1 How far can we go down the path of cleaning up Singletons without having a > DI framework in the mix? We can do DI without a framework, by just passing the

[jira] [Created] (GEODE-2987) document finer grained security migration

Swapnil Bawaskar created GEODE-2987: --- Summary: document finer grained security migration Key: GEODE-2987 URL: https://issues.apache.org/jira/browse/GEODE-2987 Project: Geode Issue Type:

[GitHub] geode pull request #536: GEODE-2977: make group/name option values consisten...

GitHub user YehEmily opened a pull request: https://github.com/apache/geode/pull/536 GEODE-2977: make group/name option values consistent Thank you for submitting a contribution to Apache Geode. In order to streamline the review of the contribution we ask you to ensure

Re: What to do with the geode-spark-connector

Perhaps the bigger question is, is anyone even using the connector? No sense in supporting something that isn't used by anyone when those efforts could be utilized elsewhere (e.g. Redis Protocol Adapter/Data Structures). On Thu, May 25, 2017 at 8:52 AM, Mark Bretl wrote: > I

Re: What to do with the geode-spark-connector

I agree with Mark and Anthony ... +1 to deleting this altogether. On Thu, May 25, 2017 at 9:12 AM, John Blum wrote: > Perhaps the bigger question is, is anyone even using the connector? No > sense in supporting something that isn't used by anyone when those efforts > could be

[GitHub] geode issue #536: GEODE-2977: make group/name option values consistent

Github user YehEmily commented on the issue: https://github.com/apache/geode/pull/536 Precheckin was successful! --- 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

[jira] [Commented] (GEODE-2977) commands should take string[] as the value for --group and --memberId(--name) whenever possible

[ https://issues.apache.org/jira/browse/GEODE-2977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16024971#comment-16024971 ] ASF GitHub Bot commented on GEODE-2977: --- GitHub user YehEmily opened a pull request:

[jira] [Commented] (GEODE-2977) commands should take string[] as the value for --group and --memberId(--name) whenever possible

[ https://issues.apache.org/jira/browse/GEODE-2977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16024973#comment-16024973 ] ASF GitHub Bot commented on GEODE-2977: --- Github user YehEmily commented on the issue:

Re: Geode Nightly build is consistently RED

@Kirk, I share your concern. If the builds are RED then we should address them. Ideally there should be no flaky tests, but given the hyper-threaded nature of the beast, things can go wrong that are really hard to reproduce. Arguably, even those scenarios should be addressed, but if we wait

Re: What to do with Singletons

+1 to moving the "OOTB" discussion onto another thread. Very distracting, interjecting another topic, into a completely not related email thread. MAYBE, there could be a list of ootb functions that the community would like to support/write. This should be done on the Apache Geode Wiki. On

Re: What to do with Singletons

+1 for Geode functions as well. Back on the day, I've talked with Barry about it and we got a few basic ones into this repository. https://github.com/markito/geode-functions But we should probably create another thread to talk about it to keep this one focused on the singletons discussion. On

[jira] [Resolved] (GEODE-2913) Update Lucene documentation

[ https://issues.apache.org/jira/browse/GEODE-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller resolved GEODE-2913. Resolution: Fixed > Update Lucene documentation > --- > >

[jira] [Resolved] (GEODE-2954) Old client gets null memberID in cache listener

[ https://issues.apache.org/jira/browse/GEODE-2954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt resolved GEODE-2954. - Resolution: Fixed > Old client gets null memberID in cache listener >

Re: Review Request 59546: GEODE-2940 Remove verification of locator host on start

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/59546/ --- (Updated May 25, 2017, 5:12 p.m.) Review request for geode, Bruce Schuchardt,

[jira] [Resolved] (GEODE-2950) Lucene index names should be restricted to valid region names since the index name becomes part of a region

[ https://issues.apache.org/jira/browse/GEODE-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Anuta resolved GEODE-2950. Resolution: Fixed Fix Version/s: 1.2.0 > Lucene index names should be restricted to valid

[jira] [Resolved] (GEODE-2952) gfsh doesn't support exact match lucene queries

[ https://issues.apache.org/jira/browse/GEODE-2952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Anuta resolved GEODE-2952. Resolution: Fixed Fix Version/s: 1.2.0 > gfsh doesn't support exact match lucene queries >

Proposal: Remove the "user-command-packages" system property

I would like to propose that we eliminate the “user-command-packages” system property, in favor of scanning the entire classpath to find commands. To give more detail, Geode currently supports three ways to load GFSH commands: Scan the classpath for commands in

[jira] [Commented] (GEODE-2957) null used as a default parameter when specifying analyzers

[ https://issues.apache.org/jira/browse/GEODE-2957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025236#comment-16025236 ] ASF GitHub Bot commented on GEODE-2957: --- Github user DivineEnder commented on the issue:

Re: Proposal: Remove the "user-command-packages" system property

imo, I think that GFSH is Spring Shell, it should really only be commands that are registered inside of META-INF.services .. aka implements CommandMarker. This way we has standard simple way to specify commands. --Udo On 5/25/17 11:52, Jared Stewart wrote: I would like to propose that we

Re: Review Request 59546: GEODE-2940 Remove verification of locator host on start

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/59546/#review176113 ---

[jira] [Reopened] (GEODE-2952) gfsh doesn't support exact match lucene queries

[ https://issues.apache.org/jira/browse/GEODE-2952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Anuta reopened GEODE-2952: > gfsh doesn't support exact match lucene queries > --- > >

  1   2   >