Index on Region

>From the cache-1.0.xsd, we noticed that an index can have element like "functional" and "primary-key", but the docs did not mention anything about it ( https://geode.apache.org/docs/guide/13/reference/topics/cache_xml.html#region). I am wondering if these are deprecated? Would it be better for

Re: Index on Region

Hi Jinmei, I am not sure whether these elements were deprecated or not. I know that they were at one time valid and a user could specify the following in their app at one point: I believe the "new" way to do this would be: How would deprecation for this work? Would your roll a new

Geode unit tests completed in 'develop/FlakyTest' with non-zero exit code

Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/FlakyTest/builds/429

Re: Index on Region

Simply searching "deprecated" in cache-1.0.xsd, we have 15 hits. Would it make sense to start creating a cache-2.0.xsd? or better yet, a server-cache-2.0.xsd and a client-cache-2.0.xsd? On Mon, Apr 16, 2018 at 2:55 PM, Patrick Rhomberg wrote: > Some types / fields have

Re: Index on Region

We should probably target removal of the "deprecated" cache xsd types/elements in Geode 2.0. I'm not sure if we can introduce cache-2.0.xsd before Geode 2.0 or not (anyone know?). On Mon, Apr 16, 2018 at 2:59 PM, Jinmei Liao wrote: > Simply searching "deprecated" in

Geode unit tests completed in 'release-1.6.0/DistributedTest' with non-zero exit code

Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1.6.0/jobs/DistributedTest/builds/5

Re: Index on Region

I don't think we have a process for deprecating elements in cache.xml yet All the changes we've had so far are additions, not removal. The reason I am asking is that we are creating POJO's (started by JAXB tool from xsd file) that would generate the cluster configuration xml automatically. As

Re: Index on Region

Some types / fields have their deprecation noted in their documentation, within the block. Alternatively / in addition, some xsd:element have the block deprecated Although I don't know if these annotations count as "visible," but they are there. On Mon, Apr 16, 2018 at 1:49 PM, Jinmei

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

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

Re: [Proposal] geode-dunit sub module.

+1 For a cleaner public dunit API. I am changing my proposal to rather create "geode-test" sub-module by combining geode-junit, geode-old-versions, and dunit test framework(extracted from geode-core). For eclipse users, I would recommend the use of buildship (rather than gradle eclipse plugin)

Re: [Proposal] geode-dunit sub module.

+1 I think I'm in favor of all of these changes as well. I don't know anything about buildship though. I do have a few dunit changes on a feature branch that I'd like to get merged to develop before we move dunit out of geode-core. I'll try to wrap up these changes by Tues or Wed. On Mon, Apr