[jira] [Commented] (GEODE-269) Remove deprecated methods on FunctionService
[ https://issues.apache.org/jira/browse/GEODE-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16037320#comment-16037320 ] ASF subversion and git services commented on GEODE-269: --- Commit 05b736442ccf716cd6de5f00fce5d221e703a5e7 in geode's branch refs/heads/develop from [~deepakddixit] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=05b7364 ] GEODE-269 : SpotlessApply changes. > Remove deprecated methods on FunctionService > > > Key: GEODE-269 > URL: https://issues.apache.org/jira/browse/GEODE-269 > Project: Geode > Issue Type: Sub-task >Reporter: Darrel Schneider >Assignee: Deepak Dixit > Original Estimate: 4h > Remaining Estimate: 4h > > FunctionService has a three deprecated methods that should be easy to remove. > All the deprecated methods have a DistributedSystem parameter. New flavors of > these methods exist that do not take the DistributedSystem since it is known > implicitly by the FunctionService. > Many tests use the deprecated methods but it should be easy to change them. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-265) Remove deprecated methods on Execution interface
[ https://issues.apache.org/jira/browse/GEODE-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16037317#comment-16037317 ] ASF subversion and git services commented on GEODE-265: --- Commit 32be4c298c04efebdf8eba18a21f6710666ef293 in geode's branch refs/heads/develop from [~deepakddixit] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=32be4c2 ] GEODE-265 : Removing implementation of methods which are deprecated and are removed from Execution interface. > Remove deprecated methods on Execution interface > > > Key: GEODE-265 > URL: https://issues.apache.org/jira/browse/GEODE-265 > Project: Geode > Issue Type: Sub-task >Reporter: Darrel Schneider >Assignee: Deepak Dixit > Original Estimate: 5h > Remaining Estimate: 5h > > The Execution interface has a number of execute methods that have been > deprecated. It looks like these could be easily removed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-265) Remove deprecated methods on Execution interface
[ https://issues.apache.org/jira/browse/GEODE-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16037316#comment-16037316 ] ASF subversion and git services commented on GEODE-265: --- Commit fe2f18d55adb028525883d2ecf1c5ceeba751385 in geode's branch refs/heads/develop from [~deepakddixit] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=fe2f18d ] GEODE-265 : Removing deprecated API's from Execution interface. In addition to execute method variants removed withArgs method which is deprecated as well. > Remove deprecated methods on Execution interface > > > Key: GEODE-265 > URL: https://issues.apache.org/jira/browse/GEODE-265 > Project: Geode > Issue Type: Sub-task >Reporter: Darrel Schneider >Assignee: Deepak Dixit > Original Estimate: 5h > Remaining Estimate: 5h > > The Execution interface has a number of execute methods that have been > deprecated. It looks like these could be easily removed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-269) Remove deprecated methods on FunctionService
[ https://issues.apache.org/jira/browse/GEODE-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16037318#comment-16037318 ] ASF subversion and git services commented on GEODE-269: --- Commit ad9e30254d0d0d39ecda94b04ae8b8eedce95d36 in geode's branch refs/heads/develop from [~deepakddixit] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=ad9e302 ] GEODE-269 : Fixing RollingUpgrade2DUnitTest. After removing deprecated API withArgs, setArgument alternative API is not available in older version of server causing NoSuchMethodFound exception. The role of setArgument with function is passing class name to load inside the function. As the relevant function is used on in the context of this test, instead of using setArgument method made class name as a field in GetDataSerializableFunction. > Remove deprecated methods on FunctionService > > > Key: GEODE-269 > URL: https://issues.apache.org/jira/browse/GEODE-269 > Project: Geode > Issue Type: Sub-task >Reporter: Darrel Schneider >Assignee: Deepak Dixit > Original Estimate: 4h > Remaining Estimate: 4h > > FunctionService has a three deprecated methods that should be easy to remove. > All the deprecated methods have a DistributedSystem parameter. New flavors of > these methods exist that do not take the DistributedSystem since it is known > implicitly by the FunctionService. > Many tests use the deprecated methods but it should be easy to change them. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-265) Remove deprecated methods on Execution interface
[ https://issues.apache.org/jira/browse/GEODE-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16037321#comment-16037321 ] ASF subversion and git services commented on GEODE-265: --- Commit 3110bd04c6d486e5d406eab9fed6f84cc4d5f790 in geode's branch refs/heads/develop from [~deepakddixit] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=3110bd0 ] GEODE-265 : Reverting removal deprecation of withArgs from Execution interface. This closes #509 > Remove deprecated methods on Execution interface > > > Key: GEODE-265 > URL: https://issues.apache.org/jira/browse/GEODE-265 > Project: Geode > Issue Type: Sub-task >Reporter: Darrel Schneider >Assignee: Deepak Dixit > Original Estimate: 5h > Remaining Estimate: 5h > > The Execution interface has a number of execute methods that have been > deprecated. It looks like these could be easily removed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2981) Fix the line feed code of the test expected value
[ https://issues.apache.org/jira/browse/GEODE-2981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16037068#comment-16037068 ] ASF subversion and git services commented on GEODE-2981: Commit c870c99097ca3722a8a0385e93cc5544c06fa565 in geode's branch refs/heads/develop from [~masaki.yamakawa] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=c870c99 ] GEODE-2981: Fix the line feed code of the test expected value * Fixed the line feed code of the test expectation value so that it does not depend on the runtime environment. * this closes #530 > Fix the line feed code of the test expected value > - > > Key: GEODE-2981 > URL: https://issues.apache.org/jira/browse/GEODE-2981 > Project: Geode > Issue Type: Test > Components: management, tests >Reporter: Masaki Yamakawa >Priority: Minor > > I mainly use the Windows. When I run the test on Windows, because Assertion > fails due to the difference in line feed code, I want to change this so that > it does not depend on the runtime environment. > The target classes are as follows: > - org.apache.geode.management.internal.cli.shell.GfshJunitTest > - org.apache.geode.management.internal.cli.help.HelpBlockUnitTest > - org.apache.geode.management.internal.cli.help.HelperUnitTest -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2947) Improve error message (seen in gfsh) when attempting to destroy a region before destroying lucene indexes
[
https://issues.apache.org/jira/browse/GEODE-2947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16035527#comment-16035527
]
ASF subversion and git services commented on GEODE-2947:
Commit 96f77fc8c9b4e76e7f88d7561bd4f31c98198ac2 in geode's branch
refs/heads/release/1.2.0 from [~karensmolermiller]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=96f77fc ]
GEODE-2947: Document revised gfsh destroy error message
This closes #555
> Improve error message (seen in gfsh) when attempting to destroy a region
> before destroying lucene indexes
> -
>
> Key: GEODE-2947
> URL: https://issues.apache.org/jira/browse/GEODE-2947
> Project: Geode
> Issue Type: Bug
> Components: docs, lucene
>Affects Versions: 1.2.0
>Reporter: Shelley Lynn Hughes-Godfrey
>Assignee: Karen Smoler Miller
> Fix For: 1.2.0
>
>
> If a user attempta to destroy region before destroying the lucene index (via
> gfsh), the error message returned is not clear. It should state that the
> lucene index should be destroyed prior to destroying the region.
> Instead it states this:
> {noformat}
> Error occurred while destroying region "testRegion". Reason: The parent
> region [/testRegion] in colocation chain cannot be destroyed, unless all its
> children [[/testIndex#_testRegion.files]] are destroyed
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (GEODE-2947) Improve error message (seen in gfsh) when attempting to destroy a region before destroying lucene indexes
[
https://issues.apache.org/jira/browse/GEODE-2947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16035524#comment-16035524
]
ASF subversion and git services commented on GEODE-2947:
Commit 74c7bbcd07a70e85b14956fa27d0c50c023a7a05 in geode's branch
refs/heads/develop from [~karensmolermiller]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=74c7bbc ]
GEODE-2947: Document revised gfsh destroy error message
This closes #555
> Improve error message (seen in gfsh) when attempting to destroy a region
> before destroying lucene indexes
> -
>
> Key: GEODE-2947
> URL: https://issues.apache.org/jira/browse/GEODE-2947
> Project: Geode
> Issue Type: Bug
> Components: docs, lucene
>Affects Versions: 1.2.0
>Reporter: Shelley Lynn Hughes-Godfrey
>Assignee: Karen Smoler Miller
> Fix For: 1.2.0
>
>
> If a user attempta to destroy region before destroying the lucene index (via
> gfsh), the error message returned is not clear. It should state that the
> lucene index should be destroyed prior to destroying the region.
> Instead it states this:
> {noformat}
> Error occurred while destroying region "testRegion". Reason: The parent
> region [/testRegion] in colocation chain cannot be destroyed, unless all its
> children [[/testIndex#_testRegion.files]] are destroyed
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (GEODE-2661) CacheListener gets invoked when an non-existent entry is removed using removeAll
[
https://issues.apache.org/jira/browse/GEODE-2661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16035504#comment-16035504
]
ASF subversion and git services commented on GEODE-2661:
Commit 39bfdccf82ccd86de99f722076d05ad542e468fc in geode's branch
refs/heads/release/1.2.0 from [~lgallinat]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=39bfdcc ]
GEODE-2661: afterDestroy events fired on non-existent keys during destroy or
removeAll.
In a client/server topology, afterDestroy events were fired on keys that did
not exist
for removeAll, remove and destroy. This suppresses those events.
cherry-pick 08451526ea5a87e15c4ce609bdf5a0f14fed7d06 from develop
> CacheListener gets invoked when an non-existent entry is removed using
> removeAll
>
>
> Key: GEODE-2661
> URL: https://issues.apache.org/jira/browse/GEODE-2661
> Project: Geode
> Issue Type: Bug
> Components: regions
>Reporter: Anilkumar Gingade
>Assignee: Lynn Gallinat
> Labels: storage_2
> Fix For: 1.2.0
>
>
> PROBLEM: CacheListener.afterDestroy is invoked for an entry which does not
> exist.
> FIX: Make entry is not a re-destroyed entry.
> When a non-existing entry is removed using removeAll from PartitionedRegion
> (need to verify this on replicated), the CacheListener's aftrerDestroy
> callback method gets invoked. The afterDestroy should not be invoked for
> entry which is not present.
> How to reproduce.
> region.put (k1, v1)
> region.put (k2, v2)
> // Remove all from client
> List keys= Arrays.asList("k1", "k2", "k8");
> region.removeAll(l);
> The afterDestroy call back will be invoked for k8. On server.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (GEODE-2935) Add Events link to Geode site footer
[
https://issues.apache.org/jira/browse/GEODE-2935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16035026#comment-16035026
]
ASF subversion and git services commented on GEODE-2935:
Commit c7f953ae870655073dac4aa68a817d369bf5e8c7 in geode-site's branch
refs/heads/asf-site from [~amb]
[ https://git-wip-us.apache.org/repos/asf?p=geode-site.git;h=c7f953a ]
GEODE-2935 Add Events link to footer, events img to Community
> Add Events link to Geode site footer
>
>
> Key: GEODE-2935
> URL: https://issues.apache.org/jira/browse/GEODE-2935
> Project: Geode
> Issue Type: Task
> Components: web-content
>Reporter: Joey McAllister
>Assignee: Joey McAllister
>Priority: Minor
> Labels: website
>
> From [~mbretl]:
> {quote}
> ASF has created a new tool for scanning TLP sites for compliance and other
> requests. The new tool is located at https://whimsy.apache.org/site, with our
> own Geode report at https://whimsy.apache.org/site/project/geode. The report
> looks good, with only one missing requirement of an Events page.
> When I searched for 'event' on the [source of the
> tool|https://gitbox.apache.org/repos/asf?p=whimsy.git;a=blob_plain;f=tools/site-scan.rb;hb=HEAD],
> I found http://www.apache.org/events/README.txt, with more event information.
> However, looking at the code, it is searching for: 'apache.org/events/'. So
> we can either create the link as text or use the image as a link.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (GEODE-3021) OQL Index isIndexedPdxKeys potential concurrency issue
[ https://issues.apache.org/jira/browse/GEODE-3021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16033680#comment-16033680 ] ASF subversion and git services commented on GEODE-3021: Commit e17ad3d226014e83d21219f2a992caaa73c55018 in geode's branch refs/heads/feature/GEODE-3021 from [~huynhja] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=e17ad3d ] GEODE-3021: Any call after the first to setPdxStringFlag should no-op * The flag isIndexedPdxKeysFlagSet is now checked before setting pdx string flag > OQL Index isIndexedPdxKeys potential concurrency issue > -- > > Key: GEODE-3021 > URL: https://issues.apache.org/jira/browse/GEODE-3021 > Project: Geode > Issue Type: Bug > Components: querying >Reporter: Jason Huynh >Assignee: Jason Huynh > > The boolean isIndexedPdxKeys is set in a synchronized method. However > multiple threads could be making a call to this method, the last caller would > set the flag based on it's key, either true or false, but the previous > callers could have meant to set it to the opposite. > This method sets isIndexedPdxKeysFlagSet afterwards and hopes that callers to > this method check this flag first. However, again, multiple threads could > have checked this flag, seen it as false, and then all attempted to call the > synchronized method. > The solution is to probably check the isIndexedPdxKeysFlagSet flag in the > method also. That way, if another thread had already completed > setPdxStringFlag(), the next call would be a no-op. > The current issue will lead to possible class cast exceptions from String to > PdxString or vice versa -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2661) CacheListener gets invoked when an non-existent entry is removed using removeAll
[
https://issues.apache.org/jira/browse/GEODE-2661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16033644#comment-16033644
]
ASF subversion and git services commented on GEODE-2661:
Commit 08451526ea5a87e15c4ce609bdf5a0f14fed7d06 in geode's branch
refs/heads/develop from [~lgallinat]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=0845152 ]
GEODE-2661: afterDestroy events fired on non-existent keys during destroy or
removeAll.
In a client/server topology, afterDestroy events were fired on keys that did
not exist
for removeAll, remove and destroy. This suppresses those events.
> CacheListener gets invoked when an non-existent entry is removed using
> removeAll
>
>
> Key: GEODE-2661
> URL: https://issues.apache.org/jira/browse/GEODE-2661
> Project: Geode
> Issue Type: Bug
> Components: regions
>Reporter: Anilkumar Gingade
>Assignee: Lynn Gallinat
> Labels: storage_2
> Fix For: 1.2.0
>
>
> When a non-existing entry is removed using removeAll from PartitionedRegion
> (need to verify this on replicated), the CacheListener's aftrerDestroy
> callback method gets invoked. The afterDestroy should not be invoked for
> entry which is not present.
> How to reproduce.
> region.put (k1, v1)
> region.put (k2, v2)
> // Remove all from client
> List keys= Arrays.asList("k1", "k2", "k8");
> region.removeAll(l);
> The afterDestroy call back will be invoked for k8. On server.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (GEODE-2892) Add sizeOnServer and isEmptyOnServer to Region
[ https://issues.apache.org/jira/browse/GEODE-2892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16033388#comment-16033388 ] ASF subversion and git services commented on GEODE-2892: Commit badd7ae51b5a381effe09f9ea9ed828494200762 in geode's branch refs/heads/release/1.2.0 from [~eshu] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=badd7ae ] GEODE-2892: Add sizeOnServer and isEmptyOnServer to Region Implement sizeOnServer and isEmptyOnServer so that ClientRegion could get size on the server. cherry-pick fbb74d8ef30269a1e40e21af0708404ad7309551 from develop > Add sizeOnServer and isEmptyOnServer to Region > -- > > Key: GEODE-2892 > URL: https://issues.apache.org/jira/browse/GEODE-2892 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Fred Krone >Assignee: Eric Shu > Labels: storage_2 > Fix For: 1.2.0 > > > To lower confusion while also not breaking backwards compatibility Region > needs explicit "onServer" methods. > sizeOnServer > isEmptyOnServer > These could also be named something like size(boolean localSize) to keep the > API a less wordy. > ACCEPTANCE: > When a developer uses these methods then the result should be from the > server-side. This includes accessor Regions. > JavaDocs should be updated accordingly. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-3018) CreateAlterDestroyRegionCommandsDUnitTest.testAlterRegionResetCacheListeners fails intermittently with AssertionError: expected: but was:
[
https://issues.apache.org/jira/browse/GEODE-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16033321#comment-16033321
]
ASF subversion and git services commented on GEODE-3018:
Commit b30545108b0522041aa4819788bd82641ade818a in geode's branch
refs/heads/develop from [~apa...@the9muses.net]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=b305451 ]
GEODE-3018: add FlakyTest category to flickering test
> CreateAlterDestroyRegionCommandsDUnitTest.testAlterRegionResetCacheListeners
> fails intermittently with AssertionError: expected: but was:
>
>
> Key: GEODE-3018
> URL: https://issues.apache.org/jira/browse/GEODE-3018
> Project: Geode
> Issue Type: Bug
> Components: gfsh, tests
>Reporter: Kirk Lund
> Labels: DeployCommand, Flaky
>
> {noformat}
> java.lang.AssertionError: expected: but was:
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:144)
> at
> org.apache.geode.management.internal.cli.commands.CreateAlterDestroyRegionCommandsDUnitTest.deployJarFilesForRegionAlter(CreateAlterDestroyRegionCommandsDUnitTest.java:1396)
> at
> org.apache.geode.management.internal.cli.commands.CreateAlterDestroyRegionCommandsDUnitTest.testAlterRegionResetCacheListeners(CreateAlterDestroyRegionCommandsDUnitTest.java:904)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> at sun.reflect.GeneratedMethodAccessor26.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
[jira] [Commented] (GEODE-2892) Add sizeOnServer and isEmptyOnServer to Region
[ https://issues.apache.org/jira/browse/GEODE-2892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16033294#comment-16033294 ] ASF subversion and git services commented on GEODE-2892: Commit fbb74d8ef30269a1e40e21af0708404ad7309551 in geode's branch refs/heads/develop from [~eshu] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=fbb74d8 ] GEODE-2892: Add sizeOnServer and isEmptyOnServer to Region Implement sizeOnServer and isEmptyOnServer so that ClientRegion could get size on the server. > Add sizeOnServer and isEmptyOnServer to Region > -- > > Key: GEODE-2892 > URL: https://issues.apache.org/jira/browse/GEODE-2892 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Fred Krone >Assignee: Eric Shu > Labels: storage_2 > Fix For: 1.2.0 > > > To lower confusion while also not breaking backwards compatibility Region > needs explicit "onServer" methods. > sizeOnServer > isEmptyOnServer > These could also be named something like size(boolean localSize) to keep the > API a less wordy. > ACCEPTANCE: > When a developer uses these methods then the result should be from the > server-side. This includes accessor Regions. > JavaDocs should be updated accordingly. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-3014) Document gfsh create lucene index and region failure sequence
[ https://issues.apache.org/jira/browse/GEODE-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16033289#comment-16033289 ] ASF subversion and git services commented on GEODE-3014: Commit 335c109d5c7d1ed427b345636c0af8b6c1636f3b in geode's branch refs/heads/release/1.2.0 from [~karensmolermiller] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=335c109 ] GEODE-3014 Document server/region/Lucene index start-up sequence This closes #554 > Document gfsh create lucene index and region failure sequence > - > > Key: GEODE-3014 > URL: https://issues.apache.org/jira/browse/GEODE-3014 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Barry Oglesby >Assignee: Karen Smoler Miller > > When creating a lucene index and region using gfsh, there is a specific > command sequence that causes the region to not be created successfully. > The sequence that fails is: > - start server(s) > - create lucene index > - start additional server(s) > - create region > What fails about this sequence is the lucene index is not saved in cluster > configuration until after the region is created. Before the region is > created, its only saved locally in existing servers. Since new servers don't > have the index when the region is created, the index definitions aren't > consistent across servers. This causes the region to be created only in some > servers (either all the original ones with the index or all the new ones > without the index). > An alternate sequence that succeeds is: > - start server(s) > - create lucene index > - create region > - start additional server(s) > Once the region has been created, then both the lucene index and region are > saved in cluster configuration, so new servers will create both the region > and index. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2966) Refactor LauncherLifecycleCommands
[
https://issues.apache.org/jira/browse/GEODE-2966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16033277#comment-16033277
]
ASF subversion and git services commented on GEODE-2966:
Commit cfdd57378fb78cbc98d41446752460f534b28db7 in geode's branch
refs/heads/release/1.2.0 from [~jstewart]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=cfdd573 ]
GEODE-2966: RefactorLauncherLifecycleCommands
- Extract several commands into their own classes.
- Extract utility methods into their own classes.
- Rename AbstractCommandsSupport to GfshCommand, and convert it from an
abstract class to an interface
(cherry picked from commit 9046c8d)
> Refactor LauncherLifecycleCommands
> --
>
> Key: GEODE-2966
> URL: https://issues.apache.org/jira/browse/GEODE-2966
> Project: Geode
> Issue Type: Sub-task
> Components: gfsh, management
>Reporter: Jared Stewart
>Assignee: Jared Stewart
> Fix For: 1.3.0
>
>
> LauncherLifecycleCommands is over 2000 lines of code, and could be made a lot
> more readable by introducing proper OO abstraction. There are also many
> private static final strings like {{CliStrings.START_LOCATOR__MEMBER_NAME}}
> that could be made shorter and more contextual, e.g.
> {{StartLocatorCommand.MEMBER_NAME}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (GEODE-2966) Refactor LauncherLifecycleCommands
[
https://issues.apache.org/jira/browse/GEODE-2966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16033278#comment-16033278
]
ASF subversion and git services commented on GEODE-2966:
Commit fd55f05c75bdcaecdae593bcab7b7b7d180402b6 in geode's branch
refs/heads/release/1.2.0 from [~jstewart]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=fd55f05 ]
GEODE-2966: Restore command changes lost in merge conflict
(cherry picked from commit ad48ab6)
> Refactor LauncherLifecycleCommands
> --
>
> Key: GEODE-2966
> URL: https://issues.apache.org/jira/browse/GEODE-2966
> Project: Geode
> Issue Type: Sub-task
> Components: gfsh, management
>Reporter: Jared Stewart
>Assignee: Jared Stewart
> Fix For: 1.3.0
>
>
> LauncherLifecycleCommands is over 2000 lines of code, and could be made a lot
> more readable by introducing proper OO abstraction. There are also many
> private static final strings like {{CliStrings.START_LOCATOR__MEMBER_NAME}}
> that could be made shorter and more contextual, e.g.
> {{StartLocatorCommand.MEMBER_NAME}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (GEODE-3014) Document gfsh create lucene index and region failure sequence
[ https://issues.apache.org/jira/browse/GEODE-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16033274#comment-16033274 ] ASF subversion and git services commented on GEODE-3014: Commit 8c81965bec2c75f66b829e674ee7269d1ed2a8a6 in geode's branch refs/heads/develop from [~karensmolermiller] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=8c81965 ] GEODE-3014 Document server/region/Lucene index start-up sequence This closes #554 > Document gfsh create lucene index and region failure sequence > - > > Key: GEODE-3014 > URL: https://issues.apache.org/jira/browse/GEODE-3014 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Barry Oglesby >Assignee: Karen Smoler Miller > > When creating a lucene index and region using gfsh, there is a specific > command sequence that causes the region to not be created successfully. > The sequence that fails is: > - start server(s) > - create lucene index > - start additional server(s) > - create region > What fails about this sequence is the lucene index is not saved in cluster > configuration until after the region is created. Before the region is > created, its only saved locally in existing servers. Since new servers don't > have the index when the region is created, the index definitions aren't > consistent across servers. This causes the region to be created only in some > servers (either all the original ones with the index or all the new ones > without the index). > An alternate sequence that succeeds is: > - start server(s) > - create lucene index > - create region > - start additional server(s) > Once the region has been created, then both the lucene index and region are > saved in cluster configuration, so new servers will create both the region > and index. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2966) Refactor LauncherLifecycleCommands
[
https://issues.apache.org/jira/browse/GEODE-2966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16033267#comment-16033267
]
ASF subversion and git services commented on GEODE-2966:
Commit ad48ab684c007b5996a942d12d63c5f405ba03f7 in geode's branch
refs/heads/develop from [~jstewart]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=ad48ab6 ]
GEODE-2966: Restore command changes lost in merge conflict
> Refactor LauncherLifecycleCommands
> --
>
> Key: GEODE-2966
> URL: https://issues.apache.org/jira/browse/GEODE-2966
> Project: Geode
> Issue Type: Sub-task
> Components: gfsh, management
>Reporter: Jared Stewart
>Assignee: Jared Stewart
> Fix For: 1.3.0
>
>
> LauncherLifecycleCommands is over 2000 lines of code, and could be made a lot
> more readable by introducing proper OO abstraction. There are also many
> private static final strings like {{CliStrings.START_LOCATOR__MEMBER_NAME}}
> that could be made shorter and more contextual, e.g.
> {{StartLocatorCommand.MEMBER_NAME}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (GEODE-2966) Refactor LauncherLifecycleCommands
[
https://issues.apache.org/jira/browse/GEODE-2966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16033214#comment-16033214
]
ASF subversion and git services commented on GEODE-2966:
Commit 9046c8dcd3bf530997fbb374085f1c1213db15e3 in geode's branch
refs/heads/develop from [~jstewart]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=9046c8d ]
GEODE-2966: RefactorLauncherLifecycleCommands
- Extract several commands into their own classes.
- Extract utility methods into their own classes.
- Rename AbstractCommandsSupport to GfshCommand, and convert it from an
abstract class to an interface
> Refactor LauncherLifecycleCommands
> --
>
> Key: GEODE-2966
> URL: https://issues.apache.org/jira/browse/GEODE-2966
> Project: Geode
> Issue Type: Sub-task
> Components: gfsh, management
>Reporter: Jared Stewart
>Assignee: Jared Stewart
>
> LauncherLifecycleCommands is over 2000 lines of code, and could be made a lot
> more readable by introducing proper OO abstraction. There are also many
> private static final strings like {{CliStrings.START_LOCATOR__MEMBER_NAME}}
> that could be made shorter and more contextual, e.g.
> {{StartLocatorCommand.MEMBER_NAME}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (GEODE-2741) Use C++11 shared pointer over custom shared pointer
[ https://issues.apache.org/jira/browse/GEODE-2741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16033147#comment-16033147 ] ASF subversion and git services commented on GEODE-2741: Commit 4fde2205851727dbbb1dd87d84aa23c508498dda in geode-native's branch refs/heads/develop from Jacob Barrett [ https://git-wip-us.apache.org/repos/asf?p=geode-native.git;h=4fde220 ] GEODE-2741: Update to Solaris Studio 12.5. > Use C++11 shared pointer over custom shared pointer > --- > > Key: GEODE-2741 > URL: https://issues.apache.org/jira/browse/GEODE-2741 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Addison >Assignee: Jacob S. Barrett > > *Context* > Now that the Native Client is compatible with C++11, we can use its shared > pointer over the custom shared pointer we use today. > *Definition of Done* > The custom shared pointer is nowhere to be found in the codebase -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-3006) busy login/logout message in the logs when gfsh connects via http
[ https://issues.apache.org/jira/browse/GEODE-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16033105#comment-16033105 ] ASF subversion and git services commented on GEODE-3006: Commit 469737b074b8f53374aa64be009fa0031150478e in geode's branch refs/heads/develop from [~jinmeiliao] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=469737b ] GEODE-3006: reduce the frequency of ping request and reduce the loglevel of login/logout messages > busy login/logout message in the logs when gfsh connects via http > - > > Key: GEODE-3006 > URL: https://issues.apache.org/jira/browse/GEODE-3006 > Project: Geode > Issue Type: Bug >Reporter: Jinmei Liao > Fix For: 1.2.0 > > > the ping request is constantly login and logout resulting in busy log > messages in the logs. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2580) New Client/Server Protocol to make the development of clients easier
[ https://issues.apache.org/jira/browse/GEODE-2580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032264#comment-16032264 ] ASF subversion and git services commented on GEODE-2580: Commit 1e9853b8be8a587ea76cc5bd427cbde213d193f0 in geode's branch refs/heads/feature/GEODE-2580 from [~ukohlmeyer] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=1e9853b ] GEODE-2580: Added Kotlin jars to geode-dependencies.jar > New Client/Server Protocol to make the development of clients easier > > > Key: GEODE-2580 > URL: https://issues.apache.org/jira/browse/GEODE-2580 > Project: Geode > Issue Type: Wish > Components: client/server >Reporter: Addison > > Today, writing a client in a new language (e.g. Go, Ruby, etc) is difficult > be the client/server protocol is now well documented and optimized for > super-low latency over maintainability. The goal of this this epic is to > write a new client/server protocol that is well documented that will be the > foundation for future Geode client. > This epic is broken down in the sub-tasks below. > Please vote on this wish if you think it is a worthwhile endeavor. > Note: no design choices are being made just yet. The first sub-task in this > epic is to make a former proposal to the developer list to discuss > foundational design choices. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2947) Improve error message (seen in gfsh) when attempting to destroy a region before destroying lucene indexes
[
https://issues.apache.org/jira/browse/GEODE-2947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032220#comment-16032220
]
ASF subversion and git services commented on GEODE-2947:
Commit 9d4465af8b1e0834f748cd64f29da12f30b34851 in geode's branch
refs/heads/release/1.2.0 from [~barry.oglesby]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=9d4465a ]
GEODE-2947: Error message is now specific to lucene indexes
(cherry picked from commit 5f4a7a905013dfa8f76f7419ea71aacae3614077)
> Improve error message (seen in gfsh) when attempting to destroy a region
> before destroying lucene indexes
> -
>
> Key: GEODE-2947
> URL: https://issues.apache.org/jira/browse/GEODE-2947
> Project: Geode
> Issue Type: Bug
> Components: lucene
>Affects Versions: 1.2.0
>Reporter: Shelley Lynn Hughes-Godfrey
> Fix For: 1.2.0
>
>
> If a user attempta to destroy region before destroying the lucene index (via
> gfsh), the error message returned is not clear. It should state that the
> lucene index should be destroyed prior to destroying the region.
> Instead it states this:
> {noformat}
> Error occurred while destroying region "testRegion". Reason: The parent
> region [/testRegion] in colocation chain cannot be destroyed, unless all its
> children [[/testIndex#_testRegion.files]] are destroyed
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (GEODE-2947) Improve error message (seen in gfsh) when attempting to destroy a region before destroying lucene indexes
[
https://issues.apache.org/jira/browse/GEODE-2947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032196#comment-16032196
]
ASF subversion and git services commented on GEODE-2947:
Commit 5f4a7a905013dfa8f76f7419ea71aacae3614077 in geode's branch
refs/heads/develop from [~barry.oglesby]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=5f4a7a9 ]
GEODE-2947: Error message is now specific to lucene indexes
> Improve error message (seen in gfsh) when attempting to destroy a region
> before destroying lucene indexes
> -
>
> Key: GEODE-2947
> URL: https://issues.apache.org/jira/browse/GEODE-2947
> Project: Geode
> Issue Type: Bug
> Components: lucene
>Affects Versions: 1.2.0
>Reporter: Shelley Lynn Hughes-Godfrey
>
> If a user attempta to destroy region before destroying the lucene index (via
> gfsh), the error message returned is not clear. It should state that the
> lucene index should be destroyed prior to destroying the region.
> Instead it states this:
> {noformat}
> Error occurred while destroying region "testRegion". Reason: The parent
> region [/testRegion] in colocation chain cannot be destroyed, unless all its
> children [[/testIndex#_testRegion.files]] are destroyed
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (GEODE-3000) Refactor Admin rest request to send credentials in Authentication header and use spring security to authenticate it.
[ https://issues.apache.org/jira/browse/GEODE-3000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032179#comment-16032179 ] ASF subversion and git services commented on GEODE-3000: Commit 5f4a797ab00d9c77567b30f09b94cfe1d8c68ba7 in geode's branch refs/heads/feature/GEODE-2632-19 from [~jinmeiliao] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=5f4a797 ] GEODE-3000: do not have jetty log at debug level > Refactor Admin rest request to send credentials in Authentication header and > use spring security to authenticate it. > > > Key: GEODE-3000 > URL: https://issues.apache.org/jira/browse/GEODE-3000 > Project: Geode > Issue Type: Improvement >Reporter: Jinmei Liao > > Currently, admin rest put security-password in the header and Jetty would log > it in debug level, we should send the authentication information in the > authentication header so that Jetty won't log them, and have the server side > be able to authenticate that way. > Currently the way these rest requests are sent are different for different > request. We need to uniform that first before we can do this refactoring. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-3011) gfsh example to do a Lucene query is incorrect
[ https://issues.apache.org/jira/browse/GEODE-3011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032183#comment-16032183 ] ASF subversion and git services commented on GEODE-3011: Commit f7e1ba2dcbe129af32d7f6226555ee09ec66d939 in geode's branch refs/heads/feature/GEODE-2632-19 from [~karensmolermiller] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=f7e1ba2 ] GEODE-3011 Correct a Lucene gfsh query example This closes #553 > gfsh example to do a Lucene query is incorrect > -- > > Key: GEODE-3011 > URL: https://issues.apache.org/jira/browse/GEODE-3011 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Diane Hardman >Assignee: Karen Smoler Miller > Fix For: 1.2.0 > > > In the Lucene integration section of the docs is the following incorrect gfsh > command example: > gfsh> lucene search --regionName=/orders -queryStrings="John*" > --defaultField=field1 > Instead it should be: > gfsh> search lucene --name=indexName --region=/orders --queryStrings="John*" > --defaultField=customer --limit=100 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2994) Doc task: interactions of backups with persistence
[ https://issues.apache.org/jira/browse/GEODE-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032182#comment-16032182 ] ASF subversion and git services commented on GEODE-2994: Commit c1288ac87f1cdee0e34441ab181eeb0506ad4554 in geode's branch refs/heads/feature/GEODE-2632-19 from [~karensmolermiller] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=c1288ac ] GEODE-2994 Take backups when region ops are quiescent This closes #544 > Doc task: interactions of backups with persistence > -- > > Key: GEODE-2994 > URL: https://issues.apache.org/jira/browse/GEODE-2994 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > Fix For: 1.2.0 > > > Document that an inconsistent state can occur by using a backup to restore > system state, if the backup is made at the wrong time. > There are 2 examples where persistence and taking a backup might cause an > inconsistency with region data, if that backup is used to restore a system. > # *A Lucene index.* The Lucene index is persistent. If a backup is unlucky > enough to be taken between a persisted write to a region (disk op) and a > persisted write to the Lucene index (disk op), then the backup represents > inconsistent data in the region and Lucene index. > # *An AEQ.* The AEQ is persistent. If a backup is unlucky enough to be taken > between a persisted write to a region (disk op) and a persisted write to the > AEQ (disk op), then the backup represents inconsistent data in the region and > the AEQ. > The solution is to make sure that backups are taken when the system is > quiescent WRT region operations. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2632) Integrated Security performance improvements
[ https://issues.apache.org/jira/browse/GEODE-2632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032184#comment-16032184 ] ASF subversion and git services commented on GEODE-2632: Commit d1ec508ee628f75d1f26dbfd6db5a237745623b5 in geode's branch refs/heads/feature/GEODE-2632-19 from [~apa...@the9muses.net] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=d1ec508 ] GEODE-2632: refactoring preparations for SecurityService and BaseCommand changes > Integrated Security performance improvements > > > Key: GEODE-2632 > URL: https://issues.apache.org/jira/browse/GEODE-2632 > Project: Geode > Issue Type: Improvement > Components: security >Reporter: Jinmei Liao >Assignee: Kirk Lund > Labels: performance > > There is a security check in Put65.cmdExecute() that, if removed, improved > the performance. > The expense of this security call needs to be reduced in order to get the > performance back. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-3002) Improve doc of (Lucene) __REGION_VALUE_FIELD
[
https://issues.apache.org/jira/browse/GEODE-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032180#comment-16032180
]
ASF subversion and git services commented on GEODE-3002:
Commit 64e4f72774e1ee811ea7f920fcb9a9598191bd4a in geode's branch
refs/heads/feature/GEODE-2632-19 from [~karensmolermiller]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=64e4f72 ]
GEODE-3002 Clarify __REGION_VALUE_FIELD in Lucene docs
This closes #550
> Improve doc of (Lucene) __REGION_VALUE_FIELD
>
>
> Key: GEODE-3002
> URL: https://issues.apache.org/jira/browse/GEODE-3002
> Project: Geode
> Issue Type: Bug
> Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Minor
> Fix For: 1.2.0
>
>
> The original description of {{__REGION_VALUE_FIELD}} is not quite right. In
> addition, there is an example gfsh command using this value that is wrong.
> It is in the {{gfsh create lucene index}} command reference page.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[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=16032178#comment-16032178
]
ASF subversion and git services commented on GEODE-2975:
Commit b89d2fb867b7f2b3aa157574bea52f53c2ae3934 in geode's branch
refs/heads/feature/GEODE-2632-19 from [~upthewaterspout]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=b89d2fb ]
GEODE-2975: Change the location of the lucene xsd
The lucene xsd was not in the right location on disk, which resulted in
a failure to validate lucene elements in the xml file.
Adding tests and validation for cases where lucene elements show up in the
wrong place, which we were unable to catch with the xsd validation.
This closes #538
> Attributes are not validated in lucene xml configuration
>
>
> Key: GEODE-2975
> URL: https://issues.apache.org/jira/browse/GEODE-2975
> Project: Geode
> Issue Type: Bug
> Components: docs, lucene
>Reporter: Barry Oglesby
>Assignee: Dan Smith
> Fix For: 1.2.0
>
>
> No exception is thrown for a lucene xml configuration missing a required
> attribute.
> No exception is thrown for a lucene xml configuration including an unknown
> attribute.
> If a {{lucene:field}} element is defined like below, no exception is thrown
> for the invalid attribute called {{namexx}} and no exceptio is thrown because
> the required attribute called {{name}} is not included.
> {noformat}
>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (GEODE-2967) Internal Errors thrown while executing queries involving self join
[ https://issues.apache.org/jira/browse/GEODE-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032181#comment-16032181 ] ASF subversion and git services commented on GEODE-2967: Commit a416a3256049210f11bc7bd6bbb1513a220a3550 in geode's branch refs/heads/feature/GEODE-2632-19 from [~nnag] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=a416a32 ] GEODE-2967: Fixing a test change * A query was modified in a test that was not intended to be changed. > Internal Errors thrown while executing queries involving self join > -- > > Key: GEODE-2967 > URL: https://issues.apache.org/jira/browse/GEODE-2967 > Project: Geode > Issue Type: Bug > Components: querying >Reporter: nabarun > > Issue: > While executing queries like > SELECT * FROM /pos p1 WHERE p1.id = p1.id > leads to an internal error if Indexes are used. > Solution: > ResultCollection needs to be created instead of StructCollection in this > particular situation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[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=16032177#comment-16032177 ] ASF subversion and git services commented on GEODE-2957: Commit 806751805cb47877b609ee35cbfa21b362a3d7b3 in geode's branch refs/heads/feature/GEODE-2632-19 from [~karensmolermiller] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=8067518 ] GEODE-2957 gfsh create lucene index "null" becomes "DEFAULT" This closes #543 > null used as a default parameter when specifying analyzers > -- > > Key: GEODE-2957 > URL: https://issues.apache.org/jira/browse/GEODE-2957 > Project: Geode > Issue Type: Bug > Components: lucene >Reporter: Jason Huynh >Assignee: David Anuta > Fix For: 1.2.0 > > > null seems to be the way to specify using the default > StandardKeywordAnalyzer. This can be used when specifying a long list of > field/analyzers. > So the line may look like > --analyzers="null,SomeAnalyzer,null,null,SomeAnalyzer} > We should probably change that to default or some other keyword. null seems > a bit confusing. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2632) Integrated Security performance improvements
[ https://issues.apache.org/jira/browse/GEODE-2632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032175#comment-16032175 ] ASF subversion and git services commented on GEODE-2632: Commit d1ec508ee628f75d1f26dbfd6db5a237745623b5 in geode's branch refs/heads/develop from [~apa...@the9muses.net] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=d1ec508 ] GEODE-2632: refactoring preparations for SecurityService and BaseCommand changes > Integrated Security performance improvements > > > Key: GEODE-2632 > URL: https://issues.apache.org/jira/browse/GEODE-2632 > Project: Geode > Issue Type: Improvement > Components: security >Reporter: Jinmei Liao >Assignee: Kirk Lund > Labels: performance > > There is a security check in Put65.cmdExecute() that, if removed, improved > the performance. > The expense of this security call needs to be reduced in order to get the > performance back. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-3011) gfsh example to do a Lucene query is incorrect
[ https://issues.apache.org/jira/browse/GEODE-3011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032092#comment-16032092 ] ASF subversion and git services commented on GEODE-3011: Commit f7e1ba2dcbe129af32d7f6226555ee09ec66d939 in geode's branch refs/heads/develop from [~karensmolermiller] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=f7e1ba2 ] GEODE-3011 Correct a Lucene gfsh query example This closes #553 > gfsh example to do a Lucene query is incorrect > -- > > Key: GEODE-3011 > URL: https://issues.apache.org/jira/browse/GEODE-3011 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Diane Hardman >Assignee: Karen Smoler Miller > > In the Lucene integration section of the docs is the following incorrect gfsh > command example: > gfsh> lucene search --regionName=/orders -queryStrings="John*" > --defaultField=field1 > Instead it should be: > gfsh> search lucene --name=indexName --region=/orders --queryStrings="John*" > --defaultField=customer --limit=100 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2994) Doc task: interactions of backups with persistence
[ https://issues.apache.org/jira/browse/GEODE-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032068#comment-16032068 ] ASF subversion and git services commented on GEODE-2994: Commit c1288ac87f1cdee0e34441ab181eeb0506ad4554 in geode's branch refs/heads/develop from [~karensmolermiller] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=c1288ac ] GEODE-2994 Take backups when region ops are quiescent This closes #544 > Doc task: interactions of backups with persistence > -- > > Key: GEODE-2994 > URL: https://issues.apache.org/jira/browse/GEODE-2994 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > > Document that an inconsistent state can occur by using a backup to restore > system state, if the backup is made at the wrong time. > There are 2 examples where persistence and taking a backup might cause an > inconsistency with region data, if that backup is used to restore a system. > # *A Lucene index.* The Lucene index is persistent. If a backup is unlucky > enough to be taken between a persisted write to a region (disk op) and a > persisted write to the Lucene index (disk op), then the backup represents > inconsistent data in the region and Lucene index. > # *An AEQ.* The AEQ is persistent. If a backup is unlucky enough to be taken > between a persisted write to a region (disk op) and a persisted write to the > AEQ (disk op), then the backup represents inconsistent data in the region and > the AEQ. > The solution is to make sure that backups are taken when the system is > quiescent WRT region operations. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2967) Internal Errors thrown while executing queries involving self join
[ https://issues.apache.org/jira/browse/GEODE-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16031617#comment-16031617 ] ASF subversion and git services commented on GEODE-2967: Commit a416a3256049210f11bc7bd6bbb1513a220a3550 in geode's branch refs/heads/develop from [~nnag] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=a416a32 ] GEODE-2967: Fixing a test change * A query was modified in a test that was not intended to be changed. > Internal Errors thrown while executing queries involving self join > -- > > Key: GEODE-2967 > URL: https://issues.apache.org/jira/browse/GEODE-2967 > Project: Geode > Issue Type: Bug > Components: querying >Reporter: nabarun > > Issue: > While executing queries like > SELECT * FROM /pos p1 WHERE p1.id = p1.id > leads to an internal error if Indexes are used. > Solution: > ResultCollection needs to be created instead of StructCollection in this > particular situation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-3002) Improve doc of (Lucene) __REGION_VALUE_FIELD
[
https://issues.apache.org/jira/browse/GEODE-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16031585#comment-16031585
]
ASF subversion and git services commented on GEODE-3002:
Commit 64e4f72774e1ee811ea7f920fcb9a9598191bd4a in geode's branch
refs/heads/develop from [~karensmolermiller]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=64e4f72 ]
GEODE-3002 Clarify __REGION_VALUE_FIELD in Lucene docs
This closes #550
> Improve doc of (Lucene) __REGION_VALUE_FIELD
>
>
> Key: GEODE-3002
> URL: https://issues.apache.org/jira/browse/GEODE-3002
> Project: Geode
> Issue Type: Bug
> Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Minor
>
> The original description of {{__REGION_VALUE_FIELD}} is not quite right. In
> addition, there is an example gfsh command using this value that is wrong.
> It is in the {{gfsh create lucene index}} command reference page.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[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=16031558#comment-16031558
]
ASF subversion and git services commented on GEODE-2975:
Commit b89d2fb867b7f2b3aa157574bea52f53c2ae3934 in geode's branch
refs/heads/develop from [~upthewaterspout]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=b89d2fb ]
GEODE-2975: Change the location of the lucene xsd
The lucene xsd was not in the right location on disk, which resulted in
a failure to validate lucene elements in the xml file.
Adding tests and validation for cases where lucene elements show up in the
wrong place, which we were unable to catch with the xsd validation.
This closes #538
> Attributes are not validated in lucene xml configuration
>
>
> Key: GEODE-2975
> URL: https://issues.apache.org/jira/browse/GEODE-2975
> Project: Geode
> Issue Type: Bug
> Components: docs, lucene
>Reporter: Barry Oglesby
> Fix For: 1.2.0
>
>
> No exception is thrown for a lucene xml configuration missing a required
> attribute.
> No exception is thrown for a lucene xml configuration including an unknown
> attribute.
> If a {{lucene:field}} element is defined like below, no exception is thrown
> for the invalid attribute called {{namexx}} and no exceptio is thrown because
> the required attribute called {{name}} is not included.
> {noformat}
>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[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=16031527#comment-16031527 ] ASF subversion and git services commented on GEODE-2957: Commit 806751805cb47877b609ee35cbfa21b362a3d7b3 in geode's branch refs/heads/feature/GEODE-1279 from [~karensmolermiller] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=8067518 ] GEODE-2957 gfsh create lucene index "null" becomes "DEFAULT" This closes #543 > null used as a default parameter when specifying analyzers > -- > > Key: GEODE-2957 > URL: https://issues.apache.org/jira/browse/GEODE-2957 > Project: Geode > Issue Type: Bug > Components: lucene >Reporter: Jason Huynh >Assignee: David Anuta > Fix For: 1.2.0 > > > null seems to be the way to specify using the default > StandardKeywordAnalyzer. This can be used when specifying a long list of > field/analyzers. > So the line may look like > --analyzers="null,SomeAnalyzer,null,null,SomeAnalyzer} > We should probably change that to default or some other keyword. null seems > a bit confusing. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (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:comment-tabpanel=16031524#comment-16031524
]
ASF subversion and git services commented on GEODE-2952:
Commit c08d70dd4695dbbad17f86fa4227a13497ab0b08 in geode's branch
refs/heads/feature/GEODE-1279 from [~karensmolermiller]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=c08d70d ]
GEODE-2952 document quoting of exact match Lucene queries
This closes #545
> gfsh doesn't support exact match lucene queries
> ---
>
> Key: GEODE-2952
> URL: https://issues.apache.org/jira/browse/GEODE-2952
> Project: Geode
> Issue Type: Bug
> Components: lucene
>Reporter: Barry Oglesby
>Assignee: David Anuta
> Fix For: 1.2.0
>
>
> This command:
> {noformat}
> gfsh>search lucene --name=index --region=data
> --defaultField=Resolution_Description --queryStrings='Police Dept'
> {noformat}
> Runs this lucene query:
> {noformat}
> Resolution_Description:police Resolution_Description:dept
> {noformat}
> I also tried this command which ran the same lucene query as above:
> {noformat}
> gfsh>search lucene --name=index --region=data
> --defaultField=Resolution_Description --queryStrings='\"Police Dept\"'
> {noformat}
> The java API supports exact match queries with "" around the queryString.
> Doing this causes this lucene query to be run:
> {noformat}
> Resolution_Description:"police dept"
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (GEODE-2420) Warn a user if they try to export too much data
[ https://issues.apache.org/jira/browse/GEODE-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16031526#comment-16031526 ] ASF subversion and git services commented on GEODE-2420: Commit 31971403c2b6442bc27f03ce4a5bcaf49cb105f7 in geode's branch refs/heads/feature/GEODE-1279 from [~dbarnes97] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=3197140 ] GEODE-2420: Warn a user if they try to export too much data - document —file-size-limit gfsh option > Warn a user if they try to export too much data > --- > > Key: GEODE-2420 > URL: https://issues.apache.org/jira/browse/GEODE-2420 > Project: Geode > Issue Type: Sub-task > Components: configuration, docs, gfsh >Reporter: Jared Stewart >Assignee: Kenneth Howe > Fix For: 1.2.0 > > > We should warn a user and prompt for confirmation before trying to perform an > `export logs` operation that would result in a file over some threshold. > (Logs and stats have the potential to be very large.) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[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=16031523#comment-16031523 ] ASF subversion and git services commented on GEODE-2941: Commit fa808acd41caa9cb76b1a5c66dd304925f31c0a2 in geode's branch refs/heads/feature/GEODE-1279 from [~dbarnes97] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=fa808ac ] GEODE-2941 Update Pulse documentation: logging info > Pulse documentation is outdated > --- > > Key: GEODE-2941 > URL: https://issues.apache.org/jira/browse/GEODE-2941 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Jinmei Liao >Assignee: Dave Barnes > Fix For: 1.2.0 > > > the pulse documentation: > http://geode.apache.org/docs/guide/11/tools_modules/pulse/quickstart.html#topic_523F6DE33FE54307BBE8F83BB7D9355D > is no longer accurate anymore. > 1. jmxUsername and jmxpassword no long applies > 2. the logging configurations has changed too. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[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=16031520#comment-16031520 ] ASF subversion and git services commented on GEODE-2957: Commit 96665fafbcc06948b7152ca9ad7344ab938f27ff in geode's branch refs/heads/feature/GEODE-1279 from [~DivineEnder] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=96665fa ] GEODE-2957: Create Lucene index analyzer help updated to include keyword DEFAULT > null used as a default parameter when specifying analyzers > -- > > Key: GEODE-2957 > URL: https://issues.apache.org/jira/browse/GEODE-2957 > Project: Geode > Issue Type: Bug > Components: lucene >Reporter: Jason Huynh >Assignee: David Anuta > Fix For: 1.2.0 > > > null seems to be the way to specify using the default > StandardKeywordAnalyzer. This can be used when specifying a long list of > field/analyzers. > So the line may look like > --analyzers="null,SomeAnalyzer,null,null,SomeAnalyzer} > We should probably change that to default or some other keyword. null seems > a bit confusing. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[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=16031522#comment-16031522 ] ASF subversion and git services commented on GEODE-2957: Commit 1ee19c759c4bdd4133f7dcf7df648f3437234a7d in geode's branch refs/heads/feature/GEODE-1279 from [~DivineEnder] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=1ee19c7 ] GEODE-2957: Create Lucene index analyzer help updated to include keyword DEFAULT This closes #547 > null used as a default parameter when specifying analyzers > -- > > Key: GEODE-2957 > URL: https://issues.apache.org/jira/browse/GEODE-2957 > Project: Geode > Issue Type: Bug > Components: lucene >Reporter: Jason Huynh >Assignee: David Anuta > Fix For: 1.2.0 > > > null seems to be the way to specify using the default > StandardKeywordAnalyzer. This can be used when specifying a long list of > field/analyzers. > So the line may look like > --analyzers="null,SomeAnalyzer,null,null,SomeAnalyzer} > We should probably change that to default or some other keyword. null seems > a bit confusing. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2974) Geode throws GemFire error
[ https://issues.apache.org/jira/browse/GEODE-2974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16031525#comment-16031525 ] ASF subversion and git services commented on GEODE-2974: Commit 2fb738157ac8b5c8e2e2fab03e3e87874f8e5bc3 in geode's branch refs/heads/feature/GEODE-1279 from [~khowe] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=2fb7381 ] GEODE-2974: Remove GemFire product name from message string The error message now reports "Could not process command due to error." followed by the decription of the error. > Geode throws GemFire error > -- > > Key: GEODE-2974 > URL: https://issues.apache.org/jira/browse/GEODE-2974 > Project: Geode > Issue Type: Bug > Components: gfsh >Reporter: Dave Barnes >Assignee: Kenneth Howe > Fix For: 1.2.0 > > > While running Geode 1.1, I ran into a problem with a gfsh command (documented > elsewhere) that gave me a GemFire error: > Could not process command due to GemFire error. Error while processing > command... > Shouldn't this say "Geode error", or better yet, "server error"? > The offending string is defined in: > geode-core/src/main/java/org/apache/geode/management/internal/cli/result/ResultBuilder.java -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[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=16031521#comment-16031521 ] ASF subversion and git services commented on GEODE-2957: Commit 5b2cdf8c1499c8fdc1f76ad9351c30876f6623b2 in geode's branch refs/heads/feature/GEODE-1279 from [~nnag] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=5b2cdf8 ] Revert "GEODE-2957: Create Lucene index analyzer help updated to include keyword DEFAULT" This reverts commit 96665fafbcc06948b7152ca9ad7344ab938f27ff. > null used as a default parameter when specifying analyzers > -- > > Key: GEODE-2957 > URL: https://issues.apache.org/jira/browse/GEODE-2957 > Project: Geode > Issue Type: Bug > Components: lucene >Reporter: Jason Huynh >Assignee: David Anuta > Fix For: 1.2.0 > > > null seems to be the way to specify using the default > StandardKeywordAnalyzer. This can be used when specifying a long list of > field/analyzers. > So the line may look like > --analyzers="null,SomeAnalyzer,null,null,SomeAnalyzer} > We should probably change that to default or some other keyword. null seems > a bit confusing. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-3013) Reduce logging level for FunctionExceptions : InternalFunctionInvocationTargetException: Multiple target nodes found for single hop operation
[
https://issues.apache.org/jira/browse/GEODE-3013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16030470#comment-16030470
]
ASF subversion and git services commented on GEODE-3013:
Commit d9f219ad048668a99ccdf4ac630326c1e13c6f19 in geode's branch
refs/heads/feature/GEODE-3013 from [~lhughesgodfrey]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=d9f219a ]
GEODE-3013: Reduce logging level for FunctionInvocationTargetException:
Multiple target nodes found for single hop operation
- Modified to display at debug vs. warning level
> Reduce logging level for FunctionExceptions :
> InternalFunctionInvocationTargetException: Multiple target nodes found for
> single hop operation
> -
>
> Key: GEODE-3013
> URL: https://issues.apache.org/jira/browse/GEODE-3013
> Project: Geode
> Issue Type: Bug
> Components: lucene
>Affects Versions: 1.2.0
>Reporter: Shelley Lynn Hughes-Godfrey
>Assignee: Shelley Lynn Hughes-Godfrey
>
> The following exception should not be logged as a warning with a full stack
> dump (as it is not actionable by the user).
> Changing this to debug log level.
> {noformat}
> Multiple target nodes found for single hop operation
> [warning 2017/04/04 14:53:06.031 PDT bridgegemfire1_monaco_15778
> tid=0x98] Exception on server while
> executing function :
> org.apache.geode.cache.lucene.internal.distributed.LuceneQueryFunction
> org.apache.geode.internal.cache.execute.InternalFunctionInvocationTargetException:
> Multiple target nodes found for single hop operation
> at
> org.apache.geode.internal.cache.PartitionedRegion.executeOnBucketSet(PartitionedRegion.java:3684)
> at
> org.apache.geode.internal.cache.PartitionedRegion.executeFunction(PartitionedRegion.java:3344)
> at
> org.apache.geode.internal.cache.execute.PartitionedRegionFunctionExecutor.executeFunction(PartitionedRegionFunctionExecutor.java:225)
> at
> org.apache.geode.internal.cache.execute.AbstractExecution.execute(AbstractExecution.java:563)
> at
> org.apache.geode.internal.cache.tier.sockets.command.ExecuteRegionFunctionSingleHop.cmdExecute(ExecuteRegionFunctionSingleHop.java:264)
> at
> org.apache.geode.internal.cache.tier.sockets.BaseCommand.execute(BaseCommand.java:141)
> at
> org.apache.geode.internal.cache.tier.sockets.ServerConnection.doNormalMsg(ServerConnection.java:783)
> at
> org.apache.geode.internal.cache.tier.sockets.ServerConnection.doOneMessage(ServerConnection.java:914)
> at
> org.apache.geode.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1171)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at
> org.apache.geode.internal.cache.tier.sockets.AcceptorImpl$1$1.run(AcceptorImpl.java:519)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[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=16030295#comment-16030295 ] ASF subversion and git services commented on GEODE-2957: Commit 806751805cb47877b609ee35cbfa21b362a3d7b3 in geode's branch refs/heads/develop from [~karensmolermiller] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=8067518 ] GEODE-2957 gfsh create lucene index "null" becomes "DEFAULT" This closes #543 > null used as a default parameter when specifying analyzers > -- > > Key: GEODE-2957 > URL: https://issues.apache.org/jira/browse/GEODE-2957 > Project: Geode > Issue Type: Bug > Components: lucene >Reporter: Jason Huynh >Assignee: David Anuta > Fix For: 1.2.0 > > > null seems to be the way to specify using the default > StandardKeywordAnalyzer. This can be used when specifying a long list of > field/analyzers. > So the line may look like > --analyzers="null,SomeAnalyzer,null,null,SomeAnalyzer} > We should probably change that to default or some other keyword. null seems > a bit confusing. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2420) Warn a user if they try to export too much data
[ https://issues.apache.org/jira/browse/GEODE-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16030264#comment-16030264 ] ASF subversion and git services commented on GEODE-2420: Commit 31971403c2b6442bc27f03ce4a5bcaf49cb105f7 in geode's branch refs/heads/develop from [~dbarnes97] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=3197140 ] GEODE-2420: Warn a user if they try to export too much data - document —file-size-limit gfsh option > Warn a user if they try to export too much data > --- > > Key: GEODE-2420 > URL: https://issues.apache.org/jira/browse/GEODE-2420 > Project: Geode > Issue Type: Sub-task > Components: configuration, docs, gfsh >Reporter: Jared Stewart >Assignee: Kenneth Howe > Fix For: 1.2.0 > > > We should warn a user and prompt for confirmation before trying to perform an > `export logs` operation that would result in a file over some threshold. > (Logs and stats have the potential to be very large.) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2974) Geode throws GemFire error
[ https://issues.apache.org/jira/browse/GEODE-2974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16030253#comment-16030253 ] ASF subversion and git services commented on GEODE-2974: Commit 2fb738157ac8b5c8e2e2fab03e3e87874f8e5bc3 in geode's branch refs/heads/develop from [~khowe] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=2fb7381 ] GEODE-2974: Remove GemFire product name from message string The error message now reports "Could not process command due to error." followed by the decription of the error. > Geode throws GemFire error > -- > > Key: GEODE-2974 > URL: https://issues.apache.org/jira/browse/GEODE-2974 > Project: Geode > Issue Type: Bug > Components: gfsh >Reporter: Dave Barnes >Assignee: Kenneth Howe > > While running Geode 1.1, I ran into a problem with a gfsh command (documented > elsewhere) that gave me a GemFire error: > Could not process command due to GemFire error. Error while processing > command... > Shouldn't this say "Geode error", or better yet, "server error"? > The offending string is defined in: > geode-core/src/main/java/org/apache/geode/management/internal/cli/result/ResultBuilder.java -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[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=16030226#comment-16030226
]
ASF subversion and git services commented on GEODE-2975:
Commit 0f96bc1b520f7442f513e2849be418b62a0b9d47 in geode-site's branch
refs/heads/master from [~upthewaterspout]
[ https://git-wip-us.apache.org/repos/asf?p=geode-site.git;h=0f96bc1 ]
GEODE-2975: Change the location of the lucene xsd
The lucene xsd was not in the correct location on the website.
Also, fixing the website generation so that it copies the xsds to the
output directory.
> Attributes are not validated in lucene xml configuration
>
>
> Key: GEODE-2975
> URL: https://issues.apache.org/jira/browse/GEODE-2975
> Project: Geode
> Issue Type: Bug
> Components: docs, lucene
>Reporter: Barry Oglesby
> Fix For: 1.2.0
>
>
> No exception is thrown for a lucene xml configuration missing a required
> attribute.
> No exception is thrown for a lucene xml configuration including an unknown
> attribute.
> If a {{lucene:field}} element is defined like below, no exception is thrown
> for the invalid attribute called {{namexx}} and no exceptio is thrown because
> the required attribute called {{name}} is not included.
> {noformat}
>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[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=16030189#comment-16030189
]
ASF subversion and git services commented on GEODE-2975:
Commit 979c64a0dfeda6a33f18ff1aade0086e1c8da56a in geode-site's branch
refs/heads/asf-site from [~upthewaterspout]
[ https://git-wip-us.apache.org/repos/asf?p=geode-site.git;h=979c64a ]
GEODE-2975: Change the location of the lucene xsd
The lucene xsd was not in the correct location on the website.
> Attributes are not validated in lucene xml configuration
>
>
> Key: GEODE-2975
> URL: https://issues.apache.org/jira/browse/GEODE-2975
> Project: Geode
> Issue Type: Bug
> Components: docs, lucene
>Reporter: Barry Oglesby
> Fix For: 1.2.0
>
>
> No exception is thrown for a lucene xml configuration missing a required
> attribute.
> No exception is thrown for a lucene xml configuration including an unknown
> attribute.
> If a {{lucene:field}} element is defined like below, no exception is thrown
> for the invalid attribute called {{namexx}} and no exceptio is thrown because
> the required attribute called {{name}} is not included.
> {noformat}
>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[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=16030150#comment-16030150
]
ASF subversion and git services commented on GEODE-2975:
Commit a67bddc19f0d126c0d87b679bb2d698dfa0faea0 in geode's branch
refs/heads/feature/GEODE-2975 from [~upthewaterspout]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=a67bddc ]
GEODE-2975 Additional tests and validation of lucene elements
Tests and validation for cases where lucene elements show up in the
wrong place, which we were unable to catch with the xsd validation.
> Attributes are not validated in lucene xml configuration
>
>
> Key: GEODE-2975
> URL: https://issues.apache.org/jira/browse/GEODE-2975
> Project: Geode
> Issue Type: Bug
> Components: docs, lucene
>Reporter: Barry Oglesby
> Fix For: 1.2.0
>
>
> No exception is thrown for a lucene xml configuration missing a required
> attribute.
> No exception is thrown for a lucene xml configuration including an unknown
> attribute.
> If a {{lucene:field}} element is defined like below, no exception is thrown
> for the invalid attribute called {{namexx}} and no exceptio is thrown because
> the required attribute called {{name}} is not included.
> {noformat}
>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (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:comment-tabpanel=16030110#comment-16030110
]
ASF subversion and git services commented on GEODE-2952:
Commit c08d70dd4695dbbad17f86fa4227a13497ab0b08 in geode's branch
refs/heads/develop from [~karensmolermiller]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=c08d70d ]
GEODE-2952 document quoting of exact match Lucene queries
This closes #545
> gfsh doesn't support exact match lucene queries
> ---
>
> Key: GEODE-2952
> URL: https://issues.apache.org/jira/browse/GEODE-2952
> Project: Geode
> Issue Type: Bug
> Components: lucene
>Reporter: Barry Oglesby
>Assignee: David Anuta
> Fix For: 1.2.0
>
>
> This command:
> {noformat}
> gfsh>search lucene --name=index --region=data
> --defaultField=Resolution_Description --queryStrings='Police Dept'
> {noformat}
> Runs this lucene query:
> {noformat}
> Resolution_Description:police Resolution_Description:dept
> {noformat}
> I also tried this command which ran the same lucene query as above:
> {noformat}
> gfsh>search lucene --name=index --region=data
> --defaultField=Resolution_Description --queryStrings='\"Police Dept\"'
> {noformat}
> The java API supports exact match queries with "" around the queryString.
> Doing this causes this lucene query to be run:
> {noformat}
> Resolution_Description:"police dept"
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[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=16030086#comment-16030086 ] ASF subversion and git services commented on GEODE-2941: Commit fa808acd41caa9cb76b1a5c66dd304925f31c0a2 in geode's branch refs/heads/develop from [~dbarnes97] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=fa808ac ] GEODE-2941 Update Pulse documentation: logging info > Pulse documentation is outdated > --- > > Key: GEODE-2941 > URL: https://issues.apache.org/jira/browse/GEODE-2941 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Jinmei Liao >Assignee: Dave Barnes > Fix For: 1.2.0 > > > the pulse documentation: > http://geode.apache.org/docs/guide/11/tools_modules/pulse/quickstart.html#topic_523F6DE33FE54307BBE8F83BB7D9355D > is no longer accurate anymore. > 1. jmxUsername and jmxpassword no long applies > 2. the logging configurations has changed too. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[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=16029983#comment-16029983 ] ASF subversion and git services commented on GEODE-2957: Commit 1ee19c759c4bdd4133f7dcf7df648f3437234a7d in geode's branch refs/heads/develop from [~DivineEnder] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=1ee19c7 ] GEODE-2957: Create Lucene index analyzer help updated to include keyword DEFAULT This closes #547 > null used as a default parameter when specifying analyzers > -- > > Key: GEODE-2957 > URL: https://issues.apache.org/jira/browse/GEODE-2957 > Project: Geode > Issue Type: Bug > Components: lucene >Reporter: Jason Huynh >Assignee: David Anuta > Fix For: 1.2.0 > > > null seems to be the way to specify using the default > StandardKeywordAnalyzer. This can be used when specifying a long list of > field/analyzers. > So the line may look like > --analyzers="null,SomeAnalyzer,null,null,SomeAnalyzer} > We should probably change that to default or some other keyword. null seems > a bit confusing. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[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=16029969#comment-16029969 ] ASF subversion and git services commented on GEODE-2957: Commit 5b2cdf8c1499c8fdc1f76ad9351c30876f6623b2 in geode's branch refs/heads/develop from [~nnag] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=5b2cdf8 ] Revert "GEODE-2957: Create Lucene index analyzer help updated to include keyword DEFAULT" This reverts commit 96665fafbcc06948b7152ca9ad7344ab938f27ff. > null used as a default parameter when specifying analyzers > -- > > Key: GEODE-2957 > URL: https://issues.apache.org/jira/browse/GEODE-2957 > Project: Geode > Issue Type: Bug > Components: lucene >Reporter: Jason Huynh >Assignee: David Anuta > Fix For: 1.2.0 > > > null seems to be the way to specify using the default > StandardKeywordAnalyzer. This can be used when specifying a long list of > field/analyzers. > So the line may look like > --analyzers="null,SomeAnalyzer,null,null,SomeAnalyzer} > We should probably change that to default or some other keyword. null seems > a bit confusing. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[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=16029964#comment-16029964 ] ASF subversion and git services commented on GEODE-2957: Commit 96665fafbcc06948b7152ca9ad7344ab938f27ff in geode's branch refs/heads/develop from [~DivineEnder] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=96665fa ] GEODE-2957: Create Lucene index analyzer help updated to include keyword DEFAULT > null used as a default parameter when specifying analyzers > -- > > Key: GEODE-2957 > URL: https://issues.apache.org/jira/browse/GEODE-2957 > Project: Geode > Issue Type: Bug > Components: lucene >Reporter: Jason Huynh >Assignee: David Anuta > Fix For: 1.2.0 > > > null seems to be the way to specify using the default > StandardKeywordAnalyzer. This can be used when specifying a long list of > field/analyzers. > So the line may look like > --analyzers="null,SomeAnalyzer,null,null,SomeAnalyzer} > We should probably change that to default or some other keyword. null seems > a bit confusing. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2960) gfsh create index should trim from field names
[ https://issues.apache.org/jira/browse/GEODE-2960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16029935#comment-16029935 ] ASF subversion and git services commented on GEODE-2960: Commit d50489c6c526ab996c4ff8883283a6e8f7a228a1 in geode's branch refs/heads/develop from [~deepakddixit] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=d50489c ] GEODE-2960 : Trim field parameter values from create lucene index. * Added logic to trim leading and trailing spaces from values provided against 'field'. * Modified existing test case to verify changes. This closes #541 > gfsh create index should trim from field names > -- > > Key: GEODE-2960 > URL: https://issues.apache.org/jira/browse/GEODE-2960 > Project: Geode > Issue Type: Bug > Components: lucene >Reporter: Jason Huynh >Assignee: Deepak Dixit > > When creating an index with specific fields, the parameter expects a comma > separated string. However we are not trimming after splitting the string. > So if fields are defined as --field="name, age, height, weight" the indexed > fields are actually "name", " age", " height", " weight" > The command should probably trim the spaces before creating the index. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2951) A gfsh lucene query specifying --pageSize fails with a NullPointerException
[
https://issues.apache.org/jira/browse/GEODE-2951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16029674#comment-16029674
]
ASF subversion and git services commented on GEODE-2951:
Commit d3543d229de46a3a582881484bccf3b77d8ac505 in geode's branch
refs/heads/develop from [~karensmolermiller]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=d3543d2 ]
GEODE-2951 Remove --pageSize from docs of gfsh search lucene
> A gfsh lucene query specifying --pageSize fails with a NullPointerException
> ---
>
> Key: GEODE-2951
> URL: https://issues.apache.org/jira/browse/GEODE-2951
> Project: Geode
> Issue Type: Bug
> Components: docs, lucene
>Reporter: Barry Oglesby
>Assignee: Karen Smoler Miller
> Fix For: 1.2.0
>
>
> A gfsh lucene query specifying {{--pageSize}} fails with a
> NullPointerException:
> {noformat}
> gfsh>search lucene --name=index --region=data --queryStrings=NYPD
> --defaultField=Agency --pageSize=10
> Could not process command due to GemFire error. An error occurred while
> searching lucene index across the Geode cluster: null
> {noformat}
> This exception is logged in the locator.log:
> {noformat}
> [info 2017/05/18 12:42:22.317 PDT locator
> tid=0x7f] null
> java.lang.NullPointerException
> at
> org.apache.geode.cache.lucene.internal.cli.LuceneIndexCommands.displayResults(LuceneIndexCommands.java:476)
> at
> org.apache.geode.cache.lucene.internal.cli.LuceneIndexCommands.searchIndex(LuceneIndexCommands.java:299)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> {noformat}
> The same query without the {{--pageSize=10}} setting works fine.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (GEODE-2580) New Client/Server Protocol to make the development of clients easier
[ https://issues.apache.org/jira/browse/GEODE-2580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16029531#comment-16029531 ] ASF subversion and git services commented on GEODE-2580: Commit ceabf07aafdfe80a424ba90cfc42fc4c3ce74594 in geode's branch refs/heads/feature/GEODE-2580 from [~ukohlmeyer] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=ceabf07 ] GEODE-2580: Amended gradle build to include protobuf files as src files > New Client/Server Protocol to make the development of clients easier > > > Key: GEODE-2580 > URL: https://issues.apache.org/jira/browse/GEODE-2580 > Project: Geode > Issue Type: Wish > Components: client/server >Reporter: Addison > > Today, writing a client in a new language (e.g. Go, Ruby, etc) is difficult > be the client/server protocol is now well documented and optimized for > super-low latency over maintainability. The goal of this this epic is to > write a new client/server protocol that is well documented that will be the > foundation for future Geode client. > This epic is broken down in the sub-tasks below. > Please vote on this wish if you think it is a worthwhile endeavor. > Note: no design choices are being made just yet. The first sub-task in this > epic is to make a former proposal to the developer list to discuss > foundational design choices. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[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=16026907#comment-16026907 ] ASF subversion and git services commented on GEODE-2941: Commit 6e56a7325336f5c9579a2ac90b7a74e760f52357 in geode's branch refs/heads/develop from [~dbarnes97] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=6e56a73 ] GEODE-2941 Pulse doc update - add logging config > Pulse documentation is outdated > --- > > Key: GEODE-2941 > URL: https://issues.apache.org/jira/browse/GEODE-2941 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Jinmei Liao >Assignee: Dave Barnes > Fix For: 1.2.0 > > > the pulse documentation: > http://geode.apache.org/docs/guide/11/tools_modules/pulse/quickstart.html#topic_523F6DE33FE54307BBE8F83BB7D9355D > is no longer accurate anymore. > 1. jmxUsername and jmxpassword no long applies > 2. the logging configurations has changed too. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[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 56f976c89fabed58a086a845593efc2ef6e75114 in geode's branch refs/heads/develop from [~eshu] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=56f976c ] GEODE-2939: Make sure bucket region initiate event tracker from the image provider. Save all event states from remote processes. Initiate event tracker from the image provider only. > Initiate bucket event tracker and get GII from different source could lead to > bucket copies inconsistence > - > > Key: GEODE-2939 > URL: https://issues.apache.org/jira/browse/GEODE-2939 > Project: Geode > Issue Type: Bug > Components: regions >Reporter: Eric Shu >Assignee: Eric Shu > Labels: storage_2 > > When a bucket region is created, it send CreateRegionMessage to all nodes > hosting the bucket data. It initiates its event tracker from the first one > replied. > In one case, it copies event tracker states from the node with primary > bucket, which is processing putAll operation and already applied a few entry > operations (so the newer seqNo is recorded for the thread performing the > putAll). > However, it gets initial image from another node -- which does not have the > entry operations yet (as putAll op is not yet being distributed to secondary > yet.) > The newly created region would receive all the putAll operations from the > primary when the primary distributes the putAll operations to secondary > copies. In the node with newly created region, some of the events would not > be applied due to hasSeenEvent method call (up to initiated last seqNo for > the said thread). This leads to bucket inconsistence among the redundant > copies. > Please note this issue would not occur if there is only one redundant copy. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[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 29ea88a23ef0feb29e8d7684c4061ac54dc66874 in geode's branch refs/heads/develop from [~DivineEnder] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=29ea88a ] GEODE-2957: Lucene create index DEFAULT keyword added for standardAnalyzer This closes #537 > null used as a default parameter when specifying analyzers > -- > > Key: GEODE-2957 > URL: https://issues.apache.org/jira/browse/GEODE-2957 > Project: Geode > Issue Type: Bug > Components: lucene >Reporter: Jason Huynh > > null seems to be the way to specify using the default > StandardKeywordAnalyzer. This can be used when specifying a long list of > field/analyzers. > So the line may look like > --analyzers="null,SomeAnalyzer,null,null,SomeAnalyzer} > We should probably change that to default or some other keyword. null seems > a bit confusing. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[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 5ab4a69378c697fdf050048165e2945a4b028eb7 in geode's branch
refs/heads/develop from [~DivineEnder]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=5ab4a69 ]
GEODE-2950: Updated error messages
* Different error messages are displayed when validating region names
versus indexes.
* Added flexible enum allowing for expanded error messages and name
validation.
This closes #540
> Lucene index names should be restricted to valid region names since the index
> name becomes part of a region
> ---
>
> Key: GEODE-2950
> URL: https://issues.apache.org/jira/browse/GEODE-2950
> Project: Geode
> Issue Type: Bug
> Components: lucene
>Reporter: Barry Oglesby
>Assignee: David Anuta
> Fix For: 1.2.0
>
>
> Currently, invalid region name characters can be used as index names. The
> index name becomes part of the async event queue id which becomes part of the
> colocated region name, so invalid characters shouldn't be allowed as index
> names. LocalRegion has a validateRegionName method that restricts the names
> to {{\[aA-zZ0-9-_.\]+}}. This method should be called to validate index names.
> Here is an example (option-j creates the ∆):
> {noformat}
> gfsh>create lucene index --name=∆∆∆ --region=data --field=text
> Member| Status
> --- | -
> 192.168.2.4(server2:53308):1025 | Successfully created lucene index
> 192.168.2.4(server1:53315):1026 | Successfully created lucene index
> {noformat}
> {noformat}
> gfsh>create region --name=data --type=PARTITION
> Member | Status
> --- | ---
> server2 | Region "/data" created on "server2"
> server1 | Region "/data" created on "server1"
> {noformat}
> {noformat}
> gfsh>put --key=0 --value=0 --region=data
> Result : true
> Key Class : java.lang.String
> Key : 0
> Value Class : java.lang.String
> Old Value :
> {noformat}
> {noformat}
> gfsh>describe lucene index --name=∆∆∆ --region=/data
> Index Name | Region Path | Server Name | Indexed Fields | Field Analyzer
> | Status| Query Executions | Updates | Commits | Documents
> -- | --- | --- | -- |
> --- | --- | | --- | ---
> | -
> ∆∆∆| /data | server1 | [text] |
> {text=StandardAnalyzer} | Initialized | 0| 0 | 0
> | 0
> ∆∆∆| /data | server2 | [text] |
> {text=StandardAnalyzer} | Initialized | 0| 1 | 1
> | 1
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[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 0fe0a1061065f07d4b734d7055f56ad1635f1a2a in geode's branch refs/heads/develop from [~lhughesgodfrey] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=0fe0a10 ] GEODE-2993: Rethrow CacheClosedException from AbstractGatewaySender.distribute() - rethrow CacheClosedException - Add test for cache close while enqueuing event in AEQ. - Add cleanup of disk dirs created by test. > Lucene query inconsistency detected after user region event fired during > cache close > > > Key: GEODE-2993 > URL: https://issues.apache.org/jira/browse/GEODE-2993 > Project: Geode > Issue Type: Bug > Components: lucene >Affects Versions: 1.2.0 >Reporter: Shelley Lynn Hughes-Godfrey > > Lucene indexes may not be updated when the member hosting the primary is > undergoing cache close while the CacheListener is being fired (resulting in > data inconsistency between user region and lucene query). > AbstractGatwaySender.distribute() simply catches and logs > CacheClosedExceptions which causes those events to be lost. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[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 c1ab3ffecb0c0a435fab64e94a97c2efc28ab085 in geode's branch refs/heads/develop from YehEmily [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=c1ab3ff ] GEODE-2977: make group/name option values consistent * this closes #536 > commands should take string[] as the value for --group and --memberId(--name) > whenever possible > --- > > Key: GEODE-2977 > URL: https://issues.apache.org/jira/browse/GEODE-2977 > Project: Geode > Issue Type: Bug > Components: gfsh >Reporter: Jinmei Liao > > some commands takes string[], and some takes only String and split them > manually. We should make this consistent and the help message would be a lot > clearer if taking string[]. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[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 5ee98401edf8e7861be1bf5af5b668fe356c0b37 in geode-native's branch refs/heads/develop from [~eburghardt] [ https://git-wip-us.apache.org/repos/asf?p=geode-native.git;h=5ee9840 ] GEODE-2992: updated URI for openssl download. > Update openssl download URI > --- > > Key: GEODE-2992 > URL: https://issues.apache.org/jira/browse/GEODE-2992 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Ernest Burghardt > > It changed again for older versions... > https://www.openssl.org/source/old/1.0.1/openssl-1.0.1u.tar.gz -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[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 7b34cfd9fd7865ee30f2d1518977b3c7bce294a4 in geode's branch refs/heads/develop from [~dbarnes97] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=7b34cfd ] GEODE-2941 Update Pulse documentation > Pulse documentation is outdated > --- > > Key: GEODE-2941 > URL: https://issues.apache.org/jira/browse/GEODE-2941 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Jinmei Liao >Assignee: Dave Barnes > > the pulse documentation: > http://geode.apache.org/docs/guide/11/tools_modules/pulse/quickstart.html#topic_523F6DE33FE54307BBE8F83BB7D9355D > is no longer accurate anymore. > 1. jmxUsername and jmxpassword no long applies > 2. the logging configurations has changed too. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[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 b7faa083aa9da5a9e7c3c579584be8f28faae02d in geode's branch
refs/heads/develop from [~DivineEnder]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=b7faa08 ]
GEODE-2944: Added __REGION_VALUE_FIELD explanation to lucene create index help
This closes #533
> lucene queries on String values (vs. objects) requires obscure/undocumented
> defaultField (__REGION_VALUE_FIELD)
> ---
>
> Key: GEODE-2944
> URL: https://issues.apache.org/jira/browse/GEODE-2944
> Project: Geode
> Issue Type: Bug
> Components: lucene
>Affects Versions: 1.2.0
>Reporter: Shelley Lynn Hughes-Godfrey
>Assignee: David Anuta
>
> When a lucene index is created, one must indicate the field to create the
> index on. When the object value is a simple String, that must be specified
> as --field=__REGION_VALUE_FIELD.
> For example,
> create lucene index --name=newIndex --region=testRegion
> --field=__REGION_VALUE_FIELD
> However, the lucene help text (for the gfsh command) does not provide this
> detail. In addition, it seems that when executing a lucene search, this must
> be entered again as --defaultField=__REGION_VALUE_FIELD.
> While this is probably not something one would use in production, I imagine
> it will be used by developers experimenting with Lucene, so we should
> consider adding this to the help text.
> {noformat}
> gfsh>help create lucene index
> NAME
> create lucene index
> IS AVAILABLE
> true
> SYNOPSIS
> Create a lucene index that can be used to execute queries.
> SYNTAX
> create lucene index --name=value --region=value --field=value(,value)*
> [--analyzer=value(,value)*]
> PARAMETERS
> name
> Name of the lucene index to create.
> Required: true
> region
> Name/Path of the region on which to create the lucene index.
> Required: true
> field
> fields on the region values which are stored in the lucene index.
> Required: true
> analyzer
> Type of the analyzer for each field.
> Required: false
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (GEODE-2990) fix testXmlCacheCreationWithPools
[ https://issues.apache.org/jira/browse/GEODE-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025302#comment-16025302 ] ASF subversion and git services commented on GEODE-2990: Commit 6708bf397485714674365c11ca9b0b9b90a8ff0f in geode-native's branch refs/heads/develop from [~eburghardt] [ https://git-wip-us.apache.org/repos/asf?p=geode-native.git;h=6708bf3 ] GEODE-2990: fix for testXMLCreationWithPools test failure > fix testXmlCacheCreationWithPools > - > > Key: GEODE-2990 > URL: https://issues.apache.org/jira/browse/GEODE-2990 > Project: Geode > Issue Type: Bug >Reporter: Ernest Burghardt > > Fails due to an initialization ordering issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[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 c793f74c07c3488ba188ed927144be688bd50b19 in geode's branch
refs/heads/develop from [~DivineEnder]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=c793f74 ]
GEODE-2950: Adding validation checks on create lucene index parameter names
This closes #532
> Lucene index names should be restricted to valid region names since the index
> name becomes part of a region
> ---
>
> Key: GEODE-2950
> URL: https://issues.apache.org/jira/browse/GEODE-2950
> Project: Geode
> Issue Type: Bug
> Components: lucene
>Reporter: Barry Oglesby
>Assignee: David Anuta
>
> Currently, invalid region name characters can be used as index names. The
> index name becomes part of the async event queue id which becomes part of the
> colocated region name, so invalid characters shouldn't be allowed as index
> names. LocalRegion has a validateRegionName method that restricts the names
> to {{\[aA-zZ0-9-_.\]+}}. This method should be called to validate index names.
> Here is an example (option-j creates the ∆):
> {noformat}
> gfsh>create lucene index --name=∆∆∆ --region=data --field=text
> Member| Status
> --- | -
> 192.168.2.4(server2:53308):1025 | Successfully created lucene index
> 192.168.2.4(server1:53315):1026 | Successfully created lucene index
> {noformat}
> {noformat}
> gfsh>create region --name=data --type=PARTITION
> Member | Status
> --- | ---
> server2 | Region "/data" created on "server2"
> server1 | Region "/data" created on "server1"
> {noformat}
> {noformat}
> gfsh>put --key=0 --value=0 --region=data
> Result : true
> Key Class : java.lang.String
> Key : 0
> Value Class : java.lang.String
> Old Value :
> {noformat}
> {noformat}
> gfsh>describe lucene index --name=∆∆∆ --region=/data
> Index Name | Region Path | Server Name | Indexed Fields | Field Analyzer
> | Status| Query Executions | Updates | Commits | Documents
> -- | --- | --- | -- |
> --- | --- | | --- | ---
> | -
> ∆∆∆| /data | server1 | [text] |
> {text=StandardAnalyzer} | Initialized | 0| 0 | 0
> | 0
> ∆∆∆| /data | server2 | [text] |
> {text=StandardAnalyzer} | Initialized | 0| 1 | 1
> | 1
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[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 e79d27d7e258d2a5f0d8a3155cc1911825a90493 in geode's branch
refs/heads/develop from [~bschuchardt]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=e79d27d ]
GEODE-2954 Old client gets null memberID in cache listener
I've added a new test that demonstrates that a new-version server sends
an EventID to a client that the client is unable to deserialize
completely. It gets an error when deserializing its member ID,
causing cache listeners to get a null when requesting the ID of
the member that effected the change.
The fix is to reserialize the member ID in EventID.toData if the
destination stream is for an older version, such as a 1.1.0 client.
This ensures the proper on-wire format is used for that version of Geode.
I've also bumped up the version ordinal for 1.2 since version 59 is
marked as unusable in Version.java.
I've changed the Banner to show the version ordinal because the other
version information in the banner isn't completely trustworthy. It
looks for a GemFireVersion.properties file on the classpath to get
this information and so it may not get it from the Geode jar file
as expected.
> Old client gets null memberID in cache listener
> ---
>
> Key: GEODE-2954
> URL: https://issues.apache.org/jira/browse/GEODE-2954
> Project: Geode
> Issue Type: Bug
> Components: membership
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
> Fix For: 1.2.0
>
>
> I was doing backward compatibility testing and found a 1.0 client was getting
> a null memberID in a cache listener
> {noformat}
> [info 2017/05/18 16:27:38.957 PDT trout(bridgegemfire5_trout_2254:2254):1030 port 21051> tid=0x2f]
> Invoked util.SilenceListener for key Object_7399: afterDestroy in edge1, pid
> 2267, vmID 5, operation DESTROY
> whereIWasRegistered: 2267
> event.getKey(): Object_7399
> event.getOldValue(): (contains 6 levels, aPrimitiveLong=6409636308677575978)>
> event.getNewValue(): null
> event.getOperation().isLoad(): false
> event.getOperation().isLocalLoad(): false
> event.getOperation().isNetLoad(): false
> event.getOperation().isNetSearch(): false
> event.isConcurrencyConflict(): false
> event.getDistributedMember(): null
> event.getCallbackArgument(): null
> event.getRegion(): /testRegion
> event.getOperation().isDistributed(): true
> event.getOperation().isExpiration(): false
> event.isOriginRemote(): true
> {noformat}
> This was in an old test suite whose testing infrastructure isn't in the Geode
> repo. I'm writing a unit test to reproduce the problem.
> If you look at EventID.java you can see that it catches IOExceptions in
> deserializing the memberID of the event and returns null without logging the
> problem.
> {code}
> try {
> result = InternalDistributedMember.readEssentialData(dis);
> } catch (IOException e) {
> // nothing can be done about this
> } catch (ClassNotFoundException e) {
> // ditto
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (GEODE-2913) Update Lucene documentation
[
https://issues.apache.org/jira/browse/GEODE-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023929#comment-16023929
]
ASF subversion and git services commented on GEODE-2913:
Commit 096c22d5c73dc609651caf2887b4d95f162230ad in geode's branch
refs/heads/develop from [~karensmolermiller]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=096c22d ]
GEODE-2913 Update Lucene index documentation
> Update Lucene documentation
> ---
>
> Key: GEODE-2913
> URL: https://issues.apache.org/jira/browse/GEODE-2913
> Project: Geode
> Issue Type: Bug
> Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
> Fix For: 1.2.0
>
>
> Improvements to the code base that need to be reflected in the docs:
> * Change LuceneService.createIndex to use a factory pattern
> {code:java}
> luceneService.createIndex(region, index, ...)
> {code}
> changes to
> {code:java}
> luceneService.createIndexFactory()
> .addField("field1name")
> .addField("field2name")
> .create()
> {code}
> * Lucene indexes will *NOT* be stored in off-heap memory.
> * Document how to configure an index on accessors - you still need to create
> the Lucene index before creating the region, even though this member does not
> hold any region data.
> If the index is not defined on the accessor, an exception like this will be
> thrown while attempting to create the region:
> {quote}
> [error 2017/05/02 15:19:26.018 PDT tid=0x1]
> java.lang.IllegalStateException: Must create Lucene index full_index on
> region /data because it is defined in another member.
> Exception in thread "main" java.lang.IllegalStateException: Must create
> Lucene index full_index on region /data because it is defined in another
> member.
> at
> org.apache.geode.internal.cache.CreateRegionProcessor$CreateRegionMessage.handleCacheDistributionAdvisee(CreateRegionProcessor.java:478)
> at
> org.apache.geode.internal.cache.CreateRegionProcessor$CreateRegionMessage.process(CreateRegionProcessor.java:379)
> {quote}
> * Do not need to create a Lucene index on a client with a Proxy cache. The
> Lucene search will always be done on the server. Besides, _you can't create
> an index on a client._
> * If you configure Invalidates for region entries (alone or as part of
> expiration), these will *NOT* invalidate the Lucene indexes.
> The problem with this is the index contains the keys, but the region doesn't,
> so the query produces results that don't exist.
> In this test, the first time the query is run, it produces N valid results.
> The second time it is run it produces N empty results:
> ** load entries
> ** run query
> ** invalidate entries
> ** run query again
> * Destroying a region will *NOT* automatically destroy any Lucene index
> associated with that region. Instead, attempting to destroy a region with a
> Lucene index will throw a colocated region exception.
> An IllegalStateException is thrown:
> {quote}
> java.lang.IllegalStateException: The parent region [/data] in colocation
> chain cannot be destroyed, unless all its children
> [[/cusip_index#_data.files]] are destroyed
> at
> org.apache.geode.internal.cache.PartitionedRegion.checkForColocatedChildren(PartitionedRegion.java:7231)
> at
> org.apache.geode.internal.cache.PartitionedRegion.destroyRegion(PartitionedRegion.java:7243)
> at
> org.apache.geode.internal.cache.AbstractRegion.destroyRegion(AbstractRegion.java:308)
> at
> DestroyLuceneIndexesAndRegionFunction.destroyRegion(DestroyLuceneIndexesAndRegionFunction.java:46)
> {quote}
> * The process to change a Lucene index using gfsh:
> 1. export region data
> 2. destroy Lucene index, destroy region
> 3. create new index, create new region without user-defined business
> logic callbacks
> 4. import data with option to turn on callbacks (to invoke Lucene Async
> Event Listener to index the data)
> 5. alter region to add user-defined business logic callbacks
> * Make sure there are no references to replicated regions as they are not
> supported.
> * Document security implementation and defaults. If a user has security
> configured for their cluster, creating a Lucene index requires DATA:MANAGE
> privilege (similar to OQL), but doing Lucene queries requires DATA:WRITE
> privilege because a function is called (different from OQL which requires
> only DATA:READ privilege). Here are all the required privileges for the gfsh
> commands:
> ** create index requires DATA:MANAGE:region
> ** describe index requires CLUSTER:READ
> ** list indexes requires CLUSTER:READ
> ** search index requires DATA:WRITE
> ** destroy index requires DATA:MANAGE:region
> * A user cannot create a Lucene index on a region that has eviction
> configured with local destroy. If using Lucene indexing, eviction can
[jira] [Commented] (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:comment-tabpanel=16023851#comment-16023851 ] ASF subversion and git services commented on GEODE-2955: Commit f271667b172191429412799327ad53efed6864e4 in geode's branch refs/heads/develop from [~nnag] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=f271667 ] GEODE-2955: Added / to the allowed list of characters in region name > gfsh create lucene index command should validate the region name parameter > -- > > Key: GEODE-2955 > URL: https://issues.apache.org/jira/browse/GEODE-2955 > Project: Geode > Issue Type: Bug > Components: lucene >Reporter: Jason Huynh >Assignee: David Anuta > > The gfsh command to create the lucene index should not only validate the > lucene index name but also the region name. It currently is possible to pass > an invalid region name as a parameter. The region will then not be able to > be created. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (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:comment-tabpanel=16023804#comment-16023804 ] ASF subversion and git services commented on GEODE-2955: Commit ee9ca4e8176183a6d0128322d21c47e5c4a0ffdf in geode's branch refs/heads/develop from [~DivineEnder] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=ee9ca4e ] GEODE-2955: Validating region names when creating lucene index This closes #531 > gfsh create lucene index command should validate the region name parameter > -- > > Key: GEODE-2955 > URL: https://issues.apache.org/jira/browse/GEODE-2955 > Project: Geode > Issue Type: Bug > Components: lucene >Reporter: Jason Huynh >Assignee: David Anuta > > The gfsh command to create the lucene index should not only validate the > lucene index name but also the region name. It currently is possible to pass > an invalid region name as a parameter. The region will then not be able to > be created. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2741) Use C++11 shared pointer over custom shared pointer
[ https://issues.apache.org/jira/browse/GEODE-2741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023555#comment-16023555 ] ASF subversion and git services commented on GEODE-2741: Commit 7eea002484ea49f5690e68b57ea53a629745beba in geode-native's branch refs/heads/develop from Jacob Barrett [ https://git-wip-us.apache.org/repos/asf?p=geode-native.git;h=7eea002 ] GEODE-2741: Fixes dependency installs. - Fixes .NET 3.5 install. - Fixes ActivePerl install. > Use C++11 shared pointer over custom shared pointer > --- > > Key: GEODE-2741 > URL: https://issues.apache.org/jira/browse/GEODE-2741 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Addison >Assignee: Jacob S. Barrett > > *Context* > Now that the Native Client is compatible with C++11, we can use its shared > pointer over the custom shared pointer we use today. > *Definition of Done* > The custom shared pointer is nowhere to be found in the codebase -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2958) create replicate region with lucene index may restore destroyed defined lucene index
[ https://issues.apache.org/jira/browse/GEODE-2958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023420#comment-16023420 ] ASF subversion and git services commented on GEODE-2958: Commit 662358fdba33ce2ea99cadfe07303361b26ead56 in geode's branch refs/heads/develop from [~barry.oglesby] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=662358f ] GEODE-2958: Destroying a defined index now removes the RegionListener > create replicate region with lucene index may restore destroyed defined > lucene index > - > > Key: GEODE-2958 > URL: https://issues.apache.org/jira/browse/GEODE-2958 > Project: Geode > Issue Type: Bug > Components: lucene >Reporter: Jason Huynh > Fix For: 1.2.0 > > > Executing the below commands in gfsh will result in the destroyed index being > created. It appears that the combination of destroying the lucene index > while specifying the region name and index name, along with attempting to > create a replicate region can cause the destroyed index to be restored and > created when a partition region with the same name finally is created. > create lucene index --name="GHOST_INDEX" --region="test" --field=name > list lucene indexes > destroy lucene index --region=test --name="GHOST_INDEX" > create lucene index --name="LUCENE_INDEX" --region="test" --field=name > create region --name=test --type=REPLICATE > create region --name=test --type=PARTITION > list lucene indexes > If the --name parameter of the index was not supplied on the destroy, then > things work fine. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-1994) Change geode StringUtils to extend commons StringUtils
[ https://issues.apache.org/jira/browse/GEODE-1994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023202#comment-16023202 ] ASF subversion and git services commented on GEODE-1994: Commit dff937f32b1cb1cce6269226dc17263484685bf1 in geode's branch refs/heads/develop from [~prhomberg] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=dff937f ] GEODE-1994: Removed two references to ServerLauncher.setMemberName that are guaranteed to throw under the changes introduced by d16d192. > Change geode StringUtils to extend commons StringUtils > -- > > Key: GEODE-1994 > URL: https://issues.apache.org/jira/browse/GEODE-1994 > Project: Geode > Issue Type: Wish > Components: general, management >Reporter: Kirk Lund >Assignee: Patrick Rhomberg > > org.apache.geode.internal.lang.StringUtils duplicates some of the methods in > org.apache.commons.lang.StringUtils with some inconsistencies. > isBlank is implemented identically > isEmpty is inconsistent -- commons version returns true if string is null, > while geode version returns false if string is null -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2970) CI Failure: org.apache.geode.management.internal.cli.commands.ConfigCommandsDUnitTest.testAlterRuntimeConfigOnAllMembers
[ https://issues.apache.org/jira/browse/GEODE-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023110#comment-16023110 ] ASF subversion and git services commented on GEODE-2970: Commit ca12f781c14409ee87873f604be64d98952c0a9a in geode's branch refs/heads/develop from [~jinmeiliao] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=ca12f78 ] GEODE-2970: clearing LogWriterAppender when shutting down locator. * Do not bury the NPE in AlterRuntimeConfigFunction * destroy the LogWriterAppender when removing the locator * added test > CI Failure: > org.apache.geode.management.internal.cli.commands.ConfigCommandsDUnitTest.testAlterRuntimeConfigOnAllMembers > > > Key: GEODE-2970 > URL: https://issues.apache.org/jira/browse/GEODE-2970 > Project: Geode > Issue Type: Bug > Components: management >Reporter: Jinmei Liao >Assignee: Jinmei Liao > > https://builds.apache.org/job/Geode-nightly/840/testReport/junit/org.apache.geode.management.internal.cli.commands/ConfigCommandsDUnitTest/testAlterRuntimeConfigOnAllMembers/ > Error Message > java.lang.AssertionError: expected: but was: > Stacktrace > java.lang.AssertionError: expected: but was: > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:834) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:144) > at > org.apache.geode.management.internal.cli.commands.ConfigCommandsDUnitTest.testAlterRuntimeConfigOnAllMembers(ConfigCommandsDUnitTest.java:424) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) > at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) > at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) > at org.junit.rules.RunRules.evaluate(RunRules.java:20) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66) > at > org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) > at sun.reflect.GeneratedMethodAccessor45.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) > at > org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32) > at >
[jira] [Commented] (GEODE-2964) NPE on gfsh put command
[
https://issues.apache.org/jira/browse/GEODE-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16022098#comment-16022098
]
ASF subversion and git services commented on GEODE-2964:
Commit f9099df50ae061a158a00f1c3a69327bbf583d1a in geode's branch
refs/heads/develop from [~jinmeiliao]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=f9099df ]
GEODE-2964: add common-collections to gfsh dependencies
> NPE on gfsh put command
> ---
>
> Key: GEODE-2964
> URL: https://issues.apache.org/jira/browse/GEODE-2964
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Swapnil Bawaskar
>
> After seeing up one locator one server, I created a partitioned region and
> try to put a value in it from gfsh which resulted in a NPE:
> {noformat}
> gfsh>start locator --name=loc1
> gfsh>start server --name=serv1
> gfsh>create region --name=foo --type=PARTITION
> gfsh>put --key=1 --value=one --region=/foo
> Exception in thread "Gfsh Launcher" java.lang.NoClassDefFoundError:
> org/apache/commons/collections/CollectionUtils
> at
> org.apache.geode.management.internal.cli.commands.DataCommands.put(DataCommands.java:895)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.springframework.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:216)
> at
> org.apache.geode.management.internal.cli.remote.RemoteExecutionStrategy.execute(RemoteExecutionStrategy.java:91)
> at
> org.apache.geode.management.internal.cli.remote.CommandProcessor.executeCommand(CommandProcessor.java:113)
> at
> org.apache.geode.management.internal.cli.remote.CommandStatementImpl.process(CommandStatementImpl.java:71)
> at
> org.apache.geode.management.internal.cli.remote.MemberCommandService.processCommand(MemberCommandService.java:52)
> at
> org.apache.geode.management.internal.beans.MemberMBeanBridge.processCommand(MemberMBeanBridge.java:1597)
> at
> org.apache.geode.management.internal.beans.MemberMBean.processCommand(MemberMBean.java:404)
> at
> org.apache.geode.management.internal.beans.MemberMBean.processCommand(MemberMBean.java:397)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:71)
> at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:275)
> at
> com.sun.jmx.mbeanserver.ConvertingMethod.invokeWithOpenReturn(ConvertingMethod.java:193)
> at
> com.sun.jmx.mbeanserver.ConvertingMethod.invokeWithOpenReturn(ConvertingMethod.java:175)
> at
> com.sun.jmx.mbeanserver.MXBeanIntrospector.invokeM2(MXBeanIntrospector.java:117)
> at
> com.sun.jmx.mbeanserver.MXBeanIntrospector.invokeM2(MXBeanIntrospector.java:54)
> at
> com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237)
> at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138)
> at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252)
> at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
> at
> com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)
> at
> javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1468)
> at
> javax.management.remote.rmi.RMIConnectionImpl.access$300(RMIConnectionImpl.java:76)
> at
> javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1309)
> at
> javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1401)
> at
> javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:829)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
[jira] [Commented] (GEODE-2967) Internal Errors thrown while executing queries involving self join
[ https://issues.apache.org/jira/browse/GEODE-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16022009#comment-16022009 ] ASF subversion and git services commented on GEODE-2967: Commit 9c408681364973096cf4192255ec3f40d86b70bd in geode's branch refs/heads/feature/GEODE-2632-17 from [~nnag] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=9c40868 ] GEODE-2967: ResultCollection instead of StructCollection * If we have one runtime iterator which is in case of self joins, ResultSet or ResultBags are created * Otherwise StructBag or StructSets are used > Internal Errors thrown while executing queries involving self join > -- > > Key: GEODE-2967 > URL: https://issues.apache.org/jira/browse/GEODE-2967 > Project: Geode > Issue Type: Bug > Components: querying >Reporter: nabarun > > Issue: > While executing queries like > SELECT * FROM /pos p1 WHERE p1.id = p1.id > leads to an internal error if Indexes are used. > Solution: > ResultCollection needs to be created instead of StructCollection in this > particular situation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2961) Distinct query with an or condition may miss results
[
https://issues.apache.org/jira/browse/GEODE-2961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16022010#comment-16022010
]
ASF subversion and git services commented on GEODE-2961:
Commit 456ee15768fb08c8e1c8c5836479d27e1bc61835 in geode's branch
refs/heads/feature/GEODE-2632-17 from [~DivineEnder]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=456ee15 ]
GEODE-2961: Fixed distinct multiple OR query returning partial results
> Distinct query with an or condition may miss results
>
>
> Key: GEODE-2961
> URL: https://issues.apache.org/jira/browse/GEODE-2961
> Project: Geode
> Issue Type: Bug
> Components: querying
>Reporter: Jason Huynh
>Assignee: David Anuta
>
> Sample query where this may be an issue:
> "select id from /region where r.status in set('active') or r.name in
> set('joe')"
> The results will contain only one of the predicates.
> The issue might be:
> {noformat}
> } else if (isDistinct && !isConditioningNeeded) {
> intermediateResults = filterResults;
> {noformat}
> but it should probably read as:
> {noformat}
> } else if (isDistinct && !isConditioningNeeded) {
> intermediateResults.addAll(filterResults);
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (GEODE-2741) Use C++11 shared pointer over custom shared pointer
[ https://issues.apache.org/jira/browse/GEODE-2741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16021925#comment-16021925 ] ASF subversion and git services commented on GEODE-2741: Commit d1710133a12ba674648fd33e7eb04f1f2dce93b7 in geode-native's branch refs/heads/develop from Jacob Barrett [ https://git-wip-us.apache.org/repos/asf?p=geode-native.git;h=d171013 ] GEODE-2741: Adds .NET 3.5 runtime for NUnit tests. > Use C++11 shared pointer over custom shared pointer > --- > > Key: GEODE-2741 > URL: https://issues.apache.org/jira/browse/GEODE-2741 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Addison >Assignee: Jacob S. Barrett > > *Context* > Now that the Native Client is compatible with C++11, we can use its shared > pointer over the custom shared pointer we use today. > *Definition of Done* > The custom shared pointer is nowhere to be found in the codebase -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2961) Distinct query with an or condition may miss results
[
https://issues.apache.org/jira/browse/GEODE-2961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16021866#comment-16021866
]
ASF subversion and git services commented on GEODE-2961:
Commit 456ee15768fb08c8e1c8c5836479d27e1bc61835 in geode's branch
refs/heads/develop from [~DivineEnder]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=456ee15 ]
GEODE-2961: Fixed distinct multiple OR query returning partial results
> Distinct query with an or condition may miss results
>
>
> Key: GEODE-2961
> URL: https://issues.apache.org/jira/browse/GEODE-2961
> Project: Geode
> Issue Type: Bug
> Components: querying
>Reporter: Jason Huynh
>Assignee: David Anuta
>
> Sample query where this may be an issue:
> "select id from /region where r.status in set('active') or r.name in
> set('joe')"
> The results will contain only one of the predicates.
> The issue might be:
> {noformat}
> } else if (isDistinct && !isConditioningNeeded) {
> intermediateResults = filterResults;
> {noformat}
> but it should probably read as:
> {noformat}
> } else if (isDistinct && !isConditioningNeeded) {
> intermediateResults.addAll(filterResults);
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (GEODE-2967) Internal Errors thrown while executing queries involving self join
[ https://issues.apache.org/jira/browse/GEODE-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16021850#comment-16021850 ] ASF subversion and git services commented on GEODE-2967: Commit 9c408681364973096cf4192255ec3f40d86b70bd in geode's branch refs/heads/develop from [~nnag] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=9c40868 ] GEODE-2967: ResultCollection instead of StructCollection * If we have one runtime iterator which is in case of self joins, ResultSet or ResultBags are created * Otherwise StructBag or StructSets are used > Internal Errors thrown while executing queries involving self join > -- > > Key: GEODE-2967 > URL: https://issues.apache.org/jira/browse/GEODE-2967 > Project: Geode > Issue Type: Bug > Components: querying >Reporter: nabarun > > Issue: > While executing queries like > SELECT * FROM /pos p1 WHERE p1.id = p1.id > leads to an internal error if Indexes are used. > Solution: > ResultCollection needs to be created instead of StructCollection in this > particular situation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2951) A gfsh lucene query specifying --pageSize fails with a NullPointerException
[
https://issues.apache.org/jira/browse/GEODE-2951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16021774#comment-16021774
]
ASF subversion and git services commented on GEODE-2951:
Commit db81d9280cf9b2286294ebcfa3ee7c3418da2ce2 in geode's branch
refs/heads/develop from [~barry.oglesby]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=db81d92 ]
GEODE-2951: Removed --pageSize option
> A gfsh lucene query specifying --pageSize fails with a NullPointerException
> ---
>
> Key: GEODE-2951
> URL: https://issues.apache.org/jira/browse/GEODE-2951
> Project: Geode
> Issue Type: Bug
> Components: lucene
>Reporter: Barry Oglesby
>
> A gfsh lucene query specifying {{--pageSize}} fails with a
> NullPointerException:
> {noformat}
> gfsh>search lucene --name=index --region=data --queryStrings=NYPD
> --defaultField=Agency --pageSize=10
> Could not process command due to GemFire error. An error occurred while
> searching lucene index across the Geode cluster: null
> {noformat}
> This exception is logged in the locator.log:
> {noformat}
> [info 2017/05/18 12:42:22.317 PDT locator
> tid=0x7f] null
> java.lang.NullPointerException
> at
> org.apache.geode.cache.lucene.internal.cli.LuceneIndexCommands.displayResults(LuceneIndexCommands.java:476)
> at
> org.apache.geode.cache.lucene.internal.cli.LuceneIndexCommands.searchIndex(LuceneIndexCommands.java:299)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> {noformat}
> The same query without the {{--pageSize=10}} setting works fine.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (GEODE-2943) Invalid queryStrings cause lucene searches to hang in in PR with multiple nodes
[
https://issues.apache.org/jira/browse/GEODE-2943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16021655#comment-16021655
]
ASF subversion and git services commented on GEODE-2943:
Commit db028ac063a5701ea815ae58acbce269f1aa in geode's branch
refs/heads/develop from [~barry.oglesby]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=db028ac ]
GEODE-2943: Wildcard and space queries are now handled correctly
> Invalid queryStrings cause lucene searches to hang in in PR with multiple
> nodes
> ---
>
> Key: GEODE-2943
> URL: https://issues.apache.org/jira/browse/GEODE-2943
> Project: Geode
> Issue Type: Bug
> Components: lucene
>Affects Versions: 1.2.0
>Reporter: Shelley Lynn Hughes-Godfrey
>
> Some invalid query strings might be "*" or " ".
> When used with a single node dataStore, we see the correct Exception returned:
> {noformat}
> gfsh>search lucene --name=testIndex --region=/testRegion --queryStrings="*"
> --defaultField=__REGION_VALUE_FIELD
> Could not process command due to GemFire error. An error occurred while
> searching lucene index across the Geode cluster: Leading wildcard is not
> allowed: __REGION_VALUE_FIELD:*
> {noformat}
> However, with multiple nodes, the query hangs.
> Jason debugged this a bit and found:
> {noformat}
> org.apache.geode.InternalGemFireException: java.io.NotSerializableException:
> org.apache.lucene.queryparser.flexible.messages.MessageImpl
> at
> org.apache.geode.distributed.internal.DistributionManager.putOutgoing(DistributionManager.java:1838)
> at
> org.apache.geode.distributed.internal.ReplyMessage.send(ReplyMessage.java:111)
> at
> org.apache.geode.internal.cache.partitioned.PartitionMessage.sendReply(PartitionMessage.java:441)
> at
> org.apache.geode.internal.cache.partitioned.PartitionMessage.process(PartitionMessage.java:421)
> at
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:376)
> at
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:442)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at
> org.apache.geode.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:625)
> at
> org.apache.geode.distributed.internal.DistributionManager$9$1.run(DistributionManager.java:1071)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.io.NotSerializableException:
> org.apache.lucene.queryparser.flexible.messages.MessageImpl
> at
> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1184)
> at
> java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
> at
> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)
> at
> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
> at
> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
> at
> java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
> at
> java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:441)
> at java.lang.Throwable.writeObject(Throwable.java:985)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at
> java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:988)
> at
> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1496)
> {noformat}
> The executing node fails with
> {noformat}
> [info 2017/05/18 13:50:34.115 PDT server1
> tid=0x120] Unexpected exception during function execution on local node
> Partitioned Region
> org.apache.geode.cache.execute.FunctionException:
> org.apache.geode.cache.lucene.LuceneQueryException: Malformed lucene query:
> *asdf*
> at
> org.apache.geode.cache.lucene.internal.distributed.LuceneQueryFunction.getQuery(LuceneQueryFunction.java:163)
> at
> org.apache.geode.cache.lucene.internal.distributed.LuceneQueryFunction.execute(LuceneQueryFunction.java:87)
> at
> org.apache.geode.internal.cache.execute.AbstractExecution.executeFunctionLocally(AbstractExecution.java:332)
> at
> org.apache.geode.internal.cache.execute.AbstractExecution$1.run(AbstractExecution.java:274)
> at
>
[jira] [Commented] (GEODE-2918) ConflictingPersistentDataException is not handled properly
[ https://issues.apache.org/jira/browse/GEODE-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16021510#comment-16021510 ] ASF subversion and git services commented on GEODE-2918: Commit 3cbb6fcd08272dc6a5219e9092b34ae29eed79f3 in geode's branch refs/heads/develop from [~agingade] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=3cbb6fc ] GEODE-2918 Close cache when ConflictingPersistentDataException is thrown. During disk recovery the ConflictingPersistentDataException is not handled properly; it should have logged an error and closed the cache. When it is handled incorrectly, the cache is in inconsistent state; causing other operations to fail in unexpected ways. > ConflictingPersistentDataException is not handled properly > -- > > Key: GEODE-2918 > URL: https://issues.apache.org/jira/browse/GEODE-2918 > Project: Geode > Issue Type: Bug > Components: persistence >Reporter: Anilkumar Gingade > Labels: storage_2 > > During disk recovery the ConflictingPersistentDataException is not handled > properly; it should have logged an error and closed the cache. > When it is handled incorrectly, the cache is in inconsistent state; causing > other operations to fail in unexpected ways. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2741) Use C++11 shared pointer over custom shared pointer
[ https://issues.apache.org/jira/browse/GEODE-2741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16021470#comment-16021470 ] ASF subversion and git services commented on GEODE-2741: Commit 2796a8955e2f23a908f696a083784ebf72fe7520 in geode-native's branch refs/heads/develop from Jacob Barrett [ https://git-wip-us.apache.org/repos/asf?p=geode-native.git;h=2796a89 ] GEODE-2741: Update Linux build to JDK 8 update 131. > Use C++11 shared pointer over custom shared pointer > --- > > Key: GEODE-2741 > URL: https://issues.apache.org/jira/browse/GEODE-2741 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Addison >Assignee: Jacob S. Barrett > > *Context* > Now that the Native Client is compatible with C++11, we can use its shared > pointer over the custom shared pointer we use today. > *Definition of Done* > The custom shared pointer is nowhere to be found in the codebase -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2420) Warn a user if they try to export too much data
[ https://issues.apache.org/jira/browse/GEODE-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16021451#comment-16021451 ] ASF subversion and git services commented on GEODE-2420: Commit adbdf50f1a5986e5c75b47184f547a3e0d78f0e2 in geode's branch refs/heads/develop from [~khowe] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=adbdf50 ] GEODE-2420: Renamed methods that had signatures changed Updated javadocs for the renamed methods to explicitly call out the exceptions thrown > Warn a user if they try to export too much data > --- > > Key: GEODE-2420 > URL: https://issues.apache.org/jira/browse/GEODE-2420 > Project: Geode > Issue Type: Sub-task > Components: configuration, docs, gfsh >Reporter: Jared Stewart >Assignee: Kenneth Howe > > We should warn a user and prompt for confirmation before trying to perform an > `export logs` operation that would result in a file over some threshold. > (Logs and stats have the potential to be very large.) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2420) Warn a user if they try to export too much data
[ https://issues.apache.org/jira/browse/GEODE-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16021449#comment-16021449 ] ASF subversion and git services commented on GEODE-2420: Commit c5962aa9308764bb964e4b4160e969f2dfae062d in geode's branch refs/heads/develop from [~khowe] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=c5962aa ] GEODE-2420: Resolve conflicts with recent checkin Use InternalCache instead of GemnFireCachImpl. Refactored product and tests - Combined LogExporter and LogSizer. - Remove classes no longer needed > Warn a user if they try to export too much data > --- > > Key: GEODE-2420 > URL: https://issues.apache.org/jira/browse/GEODE-2420 > Project: Geode > Issue Type: Sub-task > Components: configuration, docs, gfsh >Reporter: Jared Stewart >Assignee: Kenneth Howe > > We should warn a user and prompt for confirmation before trying to perform an > `export logs` operation that would result in a file over some threshold. > (Logs and stats have the potential to be very large.) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2420) Warn a user if they try to export too much data
[ https://issues.apache.org/jira/browse/GEODE-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16021448#comment-16021448 ] ASF subversion and git services commented on GEODE-2420: Commit 3ce3437ddaf9c3614b11f066011ed33664259e9f in geode's branch refs/heads/develop from [~khowe] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=3ce3437 ] GEODE-2420: Enable export logs size estimation and user warning Adds 'export logs' option, --file-limit-size, to allow user to set maximun size of the epxorted logs zip file. When size checking is enabled (file-limit-size > 0) then the check will also prevent filling up the disk on each member while consolidating and filtering the logs. > Warn a user if they try to export too much data > --- > > Key: GEODE-2420 > URL: https://issues.apache.org/jira/browse/GEODE-2420 > Project: Geode > Issue Type: Sub-task > Components: configuration, docs, gfsh >Reporter: Jared Stewart >Assignee: Kenneth Howe > > We should warn a user and prompt for confirmation before trying to perform an > `export logs` operation that would result in a file over some threshold. > (Logs and stats have the potential to be very large.) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2741) Use C++11 shared pointer over custom shared pointer
[ https://issues.apache.org/jira/browse/GEODE-2741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16021298#comment-16021298 ] ASF subversion and git services commented on GEODE-2741: Commit cb9c4e21f696236e84d9228874a307083b5788ba in geode-native's branch refs/heads/develop from Jacob Barrett [ https://git-wip-us.apache.org/repos/asf?p=geode-native.git;h=cb9c4e2 ] GEODE-2741: Update Windows build to use Visual Studio 2015 / VC14. > Use C++11 shared pointer over custom shared pointer > --- > > Key: GEODE-2741 > URL: https://issues.apache.org/jira/browse/GEODE-2741 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Addison >Assignee: Jacob S. Barrett > > *Context* > Now that the Native Client is compatible with C++11, we can use its shared > pointer over the custom shared pointer we use today. > *Definition of Done* > The custom shared pointer is nowhere to be found in the codebase -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-269) Remove deprecated methods on FunctionService
[ https://issues.apache.org/jira/browse/GEODE-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16020687#comment-16020687 ] ASF subversion and git services commented on GEODE-269: --- Commit 18db4bf382ffbf16de04f5d3dc9462677af341e4 in geode's branch refs/heads/develop from [~deepakddixit] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=18db4bf ] GEODE-269 : Removing deprecated API's from FunctionService. * Modified test cases after removing deprecated API's This closes #526 > Remove deprecated methods on FunctionService > > > Key: GEODE-269 > URL: https://issues.apache.org/jira/browse/GEODE-269 > Project: Geode > Issue Type: Sub-task >Reporter: Darrel Schneider >Assignee: Deepak Dixit > Original Estimate: 4h > Remaining Estimate: 4h > > FunctionService has a three deprecated methods that should be easy to remove. > All the deprecated methods have a DistributedSystem parameter. New flavors of > these methods exist that do not take the DistributedSystem since it is known > implicitly by the FunctionService. > Many tests use the deprecated methods but it should be easy to change them. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2956) gfsh lucene create index should trim from analyzer names
[ https://issues.apache.org/jira/browse/GEODE-2956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16020664#comment-16020664 ] ASF subversion and git services commented on GEODE-2956: Commit d88d2de96cea615ba278f3503ea5f7757d3f2e14 in geode's branch refs/heads/develop from [~DivineEnder] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=d88d2de ] GEODE-2956: Trimmed analyzer strings in create index This closes #524 > gfsh lucene create index should trim from analyzer names > > > Key: GEODE-2956 > URL: https://issues.apache.org/jira/browse/GEODE-2956 > Project: Geode > Issue Type: Bug > Components: lucene >Reporter: Jason Huynh >Assignee: Jason Huynh > > When creating an index with specific analyzers, the parameter expects a comma > separated string. However this comma separated string must have no spaces > before or after the comma. If one exists, it attempts to find an analyzer > class with the starting or trailing whitespace. This leads to an even more > hard to read command. > The command should properly trim spaces before doing the class lookup. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-269) Remove deprecated methods on FunctionService
[ https://issues.apache.org/jira/browse/GEODE-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16020237#comment-16020237 ] ASF subversion and git services commented on GEODE-269: --- Commit b47450667cc608c711e94cfd84f44aef5193345a in geode's branch refs/heads/develop from [~huynhja] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=b474506 ] Revert "GEODE-269: Removing deprecated API's from FunctionService." This reverts commit 7da9047a21f6b677066a107c5d378540b5e8b3fd. Reverting pull request completely, will wait for a new pull request without conflict > Remove deprecated methods on FunctionService > > > Key: GEODE-269 > URL: https://issues.apache.org/jira/browse/GEODE-269 > Project: Geode > Issue Type: Sub-task >Reporter: Darrel Schneider >Assignee: Deepak Dixit > Original Estimate: 4h > Remaining Estimate: 4h > > FunctionService has a three deprecated methods that should be easy to remove. > All the deprecated methods have a DistributedSystem parameter. New flavors of > these methods exist that do not take the DistributedSystem since it is known > implicitly by the FunctionService. > Many tests use the deprecated methods but it should be easy to change them. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-269) Remove deprecated methods on FunctionService
[ https://issues.apache.org/jira/browse/GEODE-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16020230#comment-16020230 ] ASF subversion and git services commented on GEODE-269: --- Commit 4e3a4d762d7caaea21153bbc5c15205b0f0799d9 in geode's branch refs/heads/develop from [~nnag] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=4e3a4d7 ] Revert "Merge branch 'feature/GEODE-269' of https://github.com/deepakddixit/incubator-geode into develop" This reverts commit 227f08be636d12d5e4a268a7039acae528c341d4, reversing changes made to aa189b1a620e543c5fabf007384612f20376be4c. > Remove deprecated methods on FunctionService > > > Key: GEODE-269 > URL: https://issues.apache.org/jira/browse/GEODE-269 > Project: Geode > Issue Type: Sub-task >Reporter: Darrel Schneider >Assignee: Deepak Dixit > Original Estimate: 4h > Remaining Estimate: 4h > > FunctionService has a three deprecated methods that should be easy to remove. > All the deprecated methods have a DistributedSystem parameter. New flavors of > these methods exist that do not take the DistributedSystem since it is known > implicitly by the FunctionService. > Many tests use the deprecated methods but it should be easy to change them. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
