[jira] [Updated] (GEODE-3029) Tomcat Install Documentation has incorrect required JARs
[ https://issues.apache.org/jira/browse/GEODE-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joey McAllister updated GEODE-3029: --- Description: This page (https://geode.apache.org/docs/guide/11/tools_modules/http_session_mgmt/tomcat_installing_the_module.html) has the incorrect required JARs needed to install tomcat with geode. Currently the list is: antlr jar fastutil jar geode-core jar javax.transaction-api jar jgroups jar log4j-api jar log4j-core jar log4j-jul jar The correct list should be: antlr jar fastutil jar geode-core jar javax.transaction-api jar jgroups jar log4j-api jar log4j-core jar log4j-jul jar commons-lang jar shiro-core jar was: This page (http://gemfire.docs.pivotal.io/geode/tools_modules/http_session_mgmt/tomcat_installing_the_module.html) has the incorrect required JARs needed to install tomcat with geode. Currently the list is: antlr jar fastutil jar geode-core jar javax.transaction-api jar jgroups jar log4j-api jar log4j-core jar log4j-jul jar The correct list should be: antlr jar fastutil jar geode-core jar javax.transaction-api jar jgroups jar log4j-api jar log4j-core jar log4j-jul jar commons-lang jar shiro-core jar > Tomcat Install Documentation has incorrect required JARs > > > Key: GEODE-3029 > URL: https://issues.apache.org/jira/browse/GEODE-3029 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: David Anuta > Fix For: 1.2.0 > > > This page > (https://geode.apache.org/docs/guide/11/tools_modules/http_session_mgmt/tomcat_installing_the_module.html) > has the incorrect required JARs needed to install tomcat with geode. > Currently the list is: > antlr jar > fastutil jar > geode-core jar > javax.transaction-api jar > jgroups jar > log4j-api jar > log4j-core jar > log4j-jul jar > The correct list should be: > antlr jar > fastutil jar > geode-core jar > javax.transaction-api jar > jgroups jar > log4j-api jar > log4j-core jar > log4j-jul jar > commons-lang jar > shiro-core jar -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (GEODE-2975) Attributes are not validated in lucene xml configuration
[
https://issues.apache.org/jira/browse/GEODE-2975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joey McAllister updated GEODE-2975:
---
Component/s: docs
> Attributes are not validated in lucene xml configuration
>
>
> 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] [Updated] (GEODE-2988) create a security example
[
https://issues.apache.org/jira/browse/GEODE-2988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joey McAllister updated GEODE-2988:
---
Component/s: docs
> create a security example
> -
>
> Key: GEODE-2988
> URL: https://issues.apache.org/jira/browse/GEODE-2988
> Project: Geode
> Issue Type: Sub-task
> Components: docs, security
>Reporter: Swapnil Bawaskar
>
> create an example for demonstrating security. The example should show how to
> leverage the {{security-manager}}, register the {{AuthInitializer}} on the
> client and have recipes for various roles.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (GEODE-2933) jmx-manager-hostname-for-clients should be a gfsh option
[
https://issues.apache.org/jira/browse/GEODE-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joey McAllister updated GEODE-2933:
---
Component/s: (was: docs)
> jmx-manager-hostname-for-clients should be a gfsh option
>
>
> Key: GEODE-2933
> URL: https://issues.apache.org/jira/browse/GEODE-2933
> Project: Geode
> Issue Type: Improvement
> Components: gfsh
>Reporter: Swapnil Bawaskar
>Assignee: Jared Stewart
>
> When jmx manager is started in the cloud, the command to start the locator so
> that one can connect gfsh from outside the cloud is:
> {noformat}
> start locator --name=test
> --J=-Dgemfire.jmx-manager-hostname-for-clients=
> {noformat}
> We should make jmx-manager-hostname-for-clients a top level option to the
> {{start server}} and {{start locator}} commands.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (GEODE-2963) Document GEODE-2933: Make jmx-manager-hostname-for-clients a top-level option to start server and start locator commands
[
https://issues.apache.org/jira/browse/GEODE-2963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joey McAllister updated GEODE-2963:
---
Priority: Minor (was: Major)
> Document GEODE-2933: Make jmx-manager-hostname-for-clients a top-level option
> to start server and start locator commands
>
>
> Key: GEODE-2963
> URL: https://issues.apache.org/jira/browse/GEODE-2963
> Project: Geode
> Issue Type: Sub-task
> Components: docs
>Reporter: Joey McAllister
>Priority: Minor
>
> This is for documenting GEODE-2933 (make jmx-manager-hostname-for-clients a
> top-level option to the {{start server}} and {{start locator}} commands).
> From GEODE-2933:
> {quote}
> When jmx manager is started in the cloud, the command to start the locator so
> that one can connect gfsh from outside the cloud is:
> {noformat}
> start locator --name=test
> --J=-Dgemfire.jmx-manager-hostname-for-clients=
> {noformat}
> We should make jmx-manager-hostname-for-clients a top-level option to the
> {{start server}} and {{start locator}} commands.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (GEODE-2963) Document GEODE-2933: Make jmx-manager-hostname-for-clients a top-level option to start server and start locator commands
Joey McAllister created GEODE-2963:
--
Summary: Document GEODE-2933: Make
jmx-manager-hostname-for-clients a top-level option to start server and start
locator commands
Key: GEODE-2963
URL: https://issues.apache.org/jira/browse/GEODE-2963
Project: Geode
Issue Type: Sub-task
Components: docs
Reporter: Joey McAllister
This is for documenting GEODE-2933 (make jmx-manager-hostname-for-clients a
top-level option to the {{start server}} and {{start locator}} commands).
>From GEODE-2933:
{quote}
When jmx manager is started in the cloud, the command to start the locator so
that one can connect gfsh from outside the cloud is:
{noformat}
start locator --name=test
--J=-Dgemfire.jmx-manager-hostname-for-clients=
{noformat}
We should make jmx-manager-hostname-for-clients a top-level option to the
{{start server}} and {{start locator}} commands.
{quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (GEODE-2942) Add Search to Geode User Guide on Website
Joey McAllister created GEODE-2942: -- Summary: Add Search to Geode User Guide on Website Key: GEODE-2942 URL: https://issues.apache.org/jira/browse/GEODE-2942 Project: Geode Issue Type: New Feature Components: docs Reporter: Joey McAllister As a User Guide reader, I want to be able to search through the User Guide on the Geode website rather than going to Google.com. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (GEODE-2935) Add Events link to Geode site footer
[
https://issues.apache.org/jira/browse/GEODE-2935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joey McAllister updated GEODE-2935:
---
Priority: Minor (was: Major)
> 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] [Assigned] (GEODE-2935) Add Events link to Geode site footer
[
https://issues.apache.org/jira/browse/GEODE-2935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joey McAllister reassigned GEODE-2935:
--
Assignee: Joey McAllister
> 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
>
> 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] [Created] (GEODE-2935) Add Events link to Geode site footer
Joey McAllister created GEODE-2935:
--
Summary: 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
>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] [Updated] (GEODE-2924) move resources from DATA to CLUSTER
[ https://issues.apache.org/jira/browse/GEODE-2924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joey McAllister updated GEODE-2924: --- Component/s: (was: docs) > move resources from DATA to CLUSTER > --- > > Key: GEODE-2924 > URL: https://issues.apache.org/jira/browse/GEODE-2924 > Project: Geode > Issue Type: Sub-task > Components: security >Reporter: Swapnil Bawaskar > > As discussed in this proposal > https://cwiki.apache.org/confluence/display/GEODE/Finer+grained+security, the > only resource on DATA should be region, we should move: > 1. pdx to CLUSTER:MANAGE > 2. import cluster-configuration to CLUSTER:MANAGE > 3. LockServiceMXBean.becomeLockGrantorto CLUSTER:MANAGE > 4. list regions to CLUSTER:READ -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (GEODE-2919) Provide finer grained security
[ https://issues.apache.org/jira/browse/GEODE-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joey McAllister updated GEODE-2919: --- Component/s: docs > Provide finer grained security > -- > > Key: GEODE-2919 > URL: https://issues.apache.org/jira/browse/GEODE-2919 > Project: Geode > Issue Type: Improvement > Components: docs, security >Reporter: Swapnil Bawaskar > > In our current security model, a user with DATA:MANAGE can create regions, > create disk stores, WAN gateways etc. I think this is a very wide scope, > because an administrator may want to give create region privilege to a > developer, but not necessarily give them the ability to create disk stores or > send the data in that region over WAN. I propose that we refine the security > model to make it finer grained. > Please see this discussion on the mailing list: > https://lists.apache.org/thread.html/f96842276e93d8a6c3080ad3982c72431d62d1e7c717ebbc50941968@%3Cdev.geode.apache.org%3E -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (GEODE-2924) move resources from DATA to CLUSTER
[ https://issues.apache.org/jira/browse/GEODE-2924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joey McAllister updated GEODE-2924: --- Component/s: docs > move resources from DATA to CLUSTER > --- > > Key: GEODE-2924 > URL: https://issues.apache.org/jira/browse/GEODE-2924 > Project: Geode > Issue Type: Sub-task > Components: docs, security >Reporter: Swapnil Bawaskar > > As discussed in this proposal > https://cwiki.apache.org/confluence/display/GEODE/Finer+grained+security, the > only resource on DATA should be region, we should move: > 1. pdx to CLUSTER:MANAGE > 2. import cluster-configuration to CLUSTER:MANAGE > 3. LockServiceMXBean.becomeLockGrantorto CLUSTER:MANAGE > 4. list regions to CLUSTER:READ -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2554) Geode incubator docs are still up
[ https://issues.apache.org/jira/browse/GEODE-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16001646#comment-16001646 ] Joey McAllister commented on GEODE-2554: I think the only thing left to do for this ticket is to follow Anthony's advice to "override the install directive to prevent it from trying to run gradlew assemble." Can someone with Gradle Wrapper knowledge help with that? > Geode incubator docs are still up > - > > Key: GEODE-2554 > URL: https://issues.apache.org/jira/browse/GEODE-2554 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Galen O'Sullivan >Assignee: Joey McAllister >Priority: Minor > Fix For: 1.2.0 > > > Search engines still direct users to the Geode incubating docs, which are at: > https://geode.apache.org/docs/guide/basic_config/data_regions/managing_data_regions.html > The most recent docs have an 11 in the URL: > https://geode.apache.org/docs/guide/11/basic_config/data_regions/managing_data_regions.html > The old docs should either be taken down, or the path made to refer to > whatever the latest docs are. That way visitors won't get stuck on an ever > increasingly stale docs site. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (GEODE-2855) Document Rename Execution.withArgs to Execution.setArguments
Joey McAllister created GEODE-2855: -- Summary: Document Rename Execution.withArgs to Execution.setArguments Key: GEODE-2855 URL: https://issues.apache.org/jira/browse/GEODE-2855 Project: Geode Issue Type: Sub-task Components: docs Reporter: Joey McAllister Fix For: 1.2.0 FunctionContext has a getArguments method. withArgs should be renamed to match. See https://issues.apache.org/jira/browse/GEODE-728 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (GEODE-2554) Geode incubator docs are still up
[ https://issues.apache.org/jira/browse/GEODE-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joey McAllister updated GEODE-2554: --- Priority: Minor (was: Major) > Geode incubator docs are still up > - > > Key: GEODE-2554 > URL: https://issues.apache.org/jira/browse/GEODE-2554 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Galen O'Sullivan >Assignee: Joey McAllister >Priority: Minor > Fix For: 1.2.0 > > > Search engines still direct users to the Geode incubating docs, which are at: > https://geode.apache.org/docs/guide/basic_config/data_regions/managing_data_regions.html > The most recent docs have an 11 in the URL: > https://geode.apache.org/docs/guide/11/basic_config/data_regions/managing_data_regions.html > The old docs should either be taken down, or the path made to refer to > whatever the latest docs are. That way visitors won't get stuck on an ever > increasingly stale docs site. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (GEODE-1897) Users should be able to configure eviction through gfsh
[
https://issues.apache.org/jira/browse/GEODE-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joey McAllister updated GEODE-1897:
---
Component/s: docs
> Users should be able to configure eviction through gfsh
> ---
>
> Key: GEODE-1897
> URL: https://issues.apache.org/jira/browse/GEODE-1897
> Project: Geode
> Issue Type: Sub-task
> Components: docs, gfsh
>Reporter: Swapnil Bawaskar
>
> While creating a region in gfsh, users should be able to configure eviction
> for that region.
> All three modes of eviction should be supported:
> 1. Eviction driven by the resource manager:
> {noformat}
> gfsh>create region --name=myRegion --type=REPLICATE --eviction-enabled
> {noformat}
> 2. eviction driven by entry count in the region:
> {noformat}
> gfsh>create region --name=myRegion --type=REPLICATE
> --eviction-entry-count=1000
> {noformat}
> 3. eviction driven by bytes used:
> {noformat}
> gfsh>create region --name=myRegion --type=REPLICATE --eviction-max-memory=100m
> {noformat}
> And also specify the eviction action as
> {noformat}
> --eviction-action=overflow-to-disk or
> --eviction-action=destroy
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (GEODE-2668) Add gfsh command to destroy gateway receiver
[
https://issues.apache.org/jira/browse/GEODE-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joey McAllister updated GEODE-2668:
---
Component/s: docs
> Add gfsh command to destroy gateway receiver
>
>
> Key: GEODE-2668
> URL: https://issues.apache.org/jira/browse/GEODE-2668
> Project: Geode
> Issue Type: Sub-task
> Components: docs, gfsh
>Reporter: Swapnil Bawaskar
>
> Currently, there is a {{create gateway-receiver}} command, but no
> corresponding destroy command.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (GEODE-2819) HTTP status code 414 is not documented
[ https://issues.apache.org/jira/browse/GEODE-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joey McAllister updated GEODE-2819: --- Component/s: docs > HTTP status code 414 is not documented > -- > > Key: GEODE-2819 > URL: https://issues.apache.org/jira/browse/GEODE-2819 > Project: Geode > Issue Type: Bug > Components: docs, rest (dev) >Reporter: Michael Dodge > > Whilst consuming the REST API to do a "put all", we built a URI that is too > long and thus got a 414 HTTP status code. The documentation that we are using > (https://geode.apache.org/docs/guide/11/rest_apps/put_multiple_values_for_keys.html) > does not specify what constitutes "too long" and does not include 414 in the > Error Codes table at the bottom of the page. The former would be nice; the > latter seems necessary. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (GEODE-2103) start locator command should include --http-service-port and --http-service-bind-address
[ https://issues.apache.org/jira/browse/GEODE-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joey McAllister reopened GEODE-2103: Assignee: Joey McAllister (was: Deepak Dixit) Needs documentation updates for gfsh Commands > Start Server and Start Locator sections. > start locator command should include --http-service-port and > --http-service-bind-address > > > Key: GEODE-2103 > URL: https://issues.apache.org/jira/browse/GEODE-2103 > Project: Geode > Issue Type: Improvement > Components: docs, management >Affects Versions: 1.0.0-incubating >Reporter: Kirk Lund >Assignee: Joey McAllister > Fix For: 1.2.0 > > > To facilitate starting the Admin REST API on a Locator, start locator command > should include --http-service-port and --http-service-bind-address. > Workaround is to specify these configuration properties with --J: > --J=-Dgemfire.http-service-port= > --J=-Dgemfire.http-service-bind-address= -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (GEODE-2554) Geode incubator docs are still up
[ https://issues.apache.org/jira/browse/GEODE-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joey McAllister reopened GEODE-2554: Assignee: Joey McAllister (was: Dave Barnes) Reopening to address redirects. > Geode incubator docs are still up > - > > Key: GEODE-2554 > URL: https://issues.apache.org/jira/browse/GEODE-2554 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Galen O'Sullivan >Assignee: Joey McAllister > Fix For: 1.2.0 > > > Search engines still direct users to the Geode incubating docs, which are at: > https://geode.apache.org/docs/guide/basic_config/data_regions/managing_data_regions.html > The most recent docs have an 11 in the URL: > https://geode.apache.org/docs/guide/11/basic_config/data_regions/managing_data_regions.html > The old docs should either be taken down, or the path made to refer to > whatever the latest docs are. That way visitors won't get stuck on an ever > increasingly stale docs site. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (GEODE-2777) Change version number from 1.1 to 1.2 in docs
Joey McAllister created GEODE-2777: -- Summary: Change version number from 1.1 to 1.2 in docs Key: GEODE-2777 URL: https://issues.apache.org/jira/browse/GEODE-2777 Project: Geode Issue Type: Task Components: docs Reporter: Joey McAllister Fix For: 1.2.0 On the `develop` branch, change any reference to v1.1 to be v1.2 in the `geode-docs` and `geode-book` directories. In the `geode-book` directory, make sure to change the hrefs in the subnav from `/11/` to `/12/` and make relevant version changes to the `config.yml` file. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (GEODE-230) Remove deprecated AttributesFactory
[ https://issues.apache.org/jira/browse/GEODE-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joey McAllister updated GEODE-230: -- Component/s: docs > Remove deprecated AttributesFactory > --- > > Key: GEODE-230 > URL: https://issues.apache.org/jira/browse/GEODE-230 > Project: Geode > Issue Type: Sub-task > Components: docs >Reporter: Darrel Schneider > > Should AttributesFactory be remove since it has been deprecated since 6.5. > In that release we started telling customers to use Cache.createRegionFactory > or ClientCache.createClientRegionFactory. > However here are a couple of reasons why we might not want to get rid of > AttributesFactory: > - The corresponding PartitionAttributesFactory is not deprecated. > - We have had customers request that it not be deprecated so that they have a > way to create a RegionAttributes on a client, send it to the server in a > function, and have the function create a region using the un-deprecated > Cache.createRegionFactory(RegionAttributes). > We could argue that Cache.createRegionFactory(RegionAttributes) is not > deprecated so that given an existing region you could get its > RegionAttributes by calling Region.getAttributes. But it seems reasonable to > want to be able to create a RegionAttributes (and its nested > PartitionAttributes) without needing to create the region in the same jvm > that is creating the attributes. > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (GEODE-2769) Document how to remove all cache listeners
Joey McAllister created GEODE-2769: -- Summary: Document how to remove all cache listeners Key: GEODE-2769 URL: https://issues.apache.org/jira/browse/GEODE-2769 Project: Geode Issue Type: Sub-task Components: docs Reporter: Joey McAllister GEODE-2236 describes how to remove all cache listeners using a gfsh command. This should be documented in the user guide. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (GEODE-288) Remove deprecated Admin API
[ https://issues.apache.org/jira/browse/GEODE-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joey McAllister updated GEODE-288: -- Component/s: (was: docs) > Remove deprecated Admin API > --- > > Key: GEODE-288 > URL: https://issues.apache.org/jira/browse/GEODE-288 > Project: Geode > Issue Type: Sub-task > Components: jmx >Affects Versions: 1.0.0-incubating >Reporter: Kirk Lund >Assignee: Kirk Lund > > The Admin API (com.gemstone.gemfire.admin) and old JMX Agent have been > deprecated since GemFire 7.0. The Admin API was retired in favor of using the > new Management JMX API (com.gemstone.gemfire.management) and GFSH. > #1) move some Admin classes used internally by non-Admin code: > move com.gemstone.gemfire.admin.BackupStatus > move com.gemstone.gemfire.admin.OperationCancelledException > move com.gemstone.gemfire.admin.RegionNotFoundException > move > com.gemstone.gemfire.admin.internal.AdminDistributedSystemImpl.backupAllMembers > move > com.gemstone.gemfire.admin.internal.AdminDistributedSystemImpl.compactAllDiskStores > move com.gemstone.gemfire.admin.internal.FinishBackupRequest > move com.gemstone.gemfire.admin.internal.FlushToDiskRequest > move com.gemstone.gemfire.admin.internal.InetAddressUtil > move com.gemstone.gemfire.admin.internal.PrepareBackupRequest > #2) move com.gemstone.gemfire.admin to > com.gemstone.gemfire.internal.admin.api (temporarily) > #3) remove com.gemstone.gemfire.cache.* usage of admin > #4) remove com.gemstone.gemfire.distributed.* usage of admin > #5) remove com.gemstone.gemfire.internal.* usage of admin (except for > internal.admin.*) > #6) remove com.gemstone.gemfire.management.* usage of admin > #7) remove com.gemstone.gemfire.internal.admin.api if possible > #8) remove unused classes from com.gemstone.gemfire.internal.admin.* > Breakdown by package and class: > com.gemstone.gemfire > --change DataSerializer to use moved RegionNotFoundException > com.gemstone.gemfire.cache > com.gemstone.gemfire.cache.persistence > com.gemstone.gemfire.cache.util > --remove com.gemstone.gemfire.cache.util.UniversalMembershipListenerAdapter > com.gemstone.gemfire.distributed > --remove Admin API from javadocs in Locator and DistributedSystem > com.gemstone.gemfire.distributed.internal > --remove > com.gemstone.gemfire.distributed.internal.DistributionManager.createHealthMonitor > --remove remove com.gemstone.gemfire.distributed.internal.HealthMonitor > --remove remove com.gemstone.gemfire.distributed.internal.HealthMonitorImpl > --change > com.gemstone.gemfire.distributed.internal.InternalDistributedSystem.hasAlertListenerFor > to not use AlertLevel > com.gemstone.gemfire.internal > --remove DSFIDFactory support for admin messages > --remove com.gemstone.gemfire.admin.jmx.internal.AgentLauncher from > GemFireUtilLauncher > --change MigrationServer to use moved InetAddressUtil > --change SocketCreator to use moved InetAddressUtil > --remove SystemAdmin.backup > --remove SystemAdmin.compactAllDiskStores > --remove SystemAdmin.shutDownAll > --remove SystemAdmin.listMissingDiskStores > --remove SystemAdmin.revokeMissingDiskStores > com.gemstone.gemfire.internal.cache > --replace use of com.gemstone.gemfire.admin.OperationCancelledException > --remove use of > com.gemstone.gemfire.admin.internal.SystemMemberCacheEventProcessor > com.gemstone.gemfire.internal.cache.partitioned > --replace use of com.gemstone.gemfire.admin.OperationCancelledException > com.gemstone.gemfire.internal.cache.snapshot > --replace use of com.gemstone.gemfire.admin.RegionNotFoundException > com.gemstone.gemfire.internal.tools.gfsh.app.command.task > --reimplement PartitionedRegionAttributeTask > com.gemstone.gemfire.internal.tools.gfsh.util > --reimplement RegionUtil > com.gemstone.gemfire.management.internal.beans > --change DistributedSystemBridge to use moved classes > com.gemstone.gemfire.management.internal.cli.commands > --change DiskStoreCommands to use moved classes > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (GEODE-2554) Geode incubator docs are still up
[ https://issues.apache.org/jira/browse/GEODE-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joey McAllister reassigned GEODE-2554: -- Assignee: (was: Joey McAllister) > Geode incubator docs are still up > - > > Key: GEODE-2554 > URL: https://issues.apache.org/jira/browse/GEODE-2554 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Galen O'Sullivan > > Search engines still direct users to the Geode incubating docs, which are at: > https://geode.apache.org/docs/guide/basic_config/data_regions/managing_data_regions.html > The most recent docs have an 11 in the URL: > https://geode.apache.org/docs/guide/11/basic_config/data_regions/managing_data_regions.html > The old docs should either be taken down, or the path made to refer to > whatever the latest docs are. That way visitors won't get stuck on an ever > increasingly stale docs site. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (GEODE-2480) Need to specify correct version of CMake required for building Native Client
[ https://issues.apache.org/jira/browse/GEODE-2480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joey McAllister updated GEODE-2480: --- Component/s: (was: docs) > Need to specify correct version of CMake required for building Native Client > > > Key: GEODE-2480 > URL: https://issues.apache.org/jira/browse/GEODE-2480 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Akihiro Kitada > > According to the following doc, the version of CMake required for building > Native Client is *4.3* or newer. > https://github.com/apache/geode-native/blob/develop/BUILDING.md > However, the latest stable version of CMake is 3.7.2 as of now. Please > specify the correct version of CMake (it could be "*3.4* or newer" ?). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (GEODE-2267) Add gfsh command to export all cluster artifacts
[ https://issues.apache.org/jira/browse/GEODE-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joey McAllister updated GEODE-2267: --- Component/s: (was: docs) > Add gfsh command to export all cluster artifacts > > > Key: GEODE-2267 > URL: https://issues.apache.org/jira/browse/GEODE-2267 > Project: Geode > Issue Type: New Feature > Components: configuration, gfsh >Reporter: Diane Hardman > Labels: ExportClusterArtifacts, export, gfsh, logging, statistics > > We would like a single gfsh command to collect and export all logfiles and > stat files into a single package. This package (zipfile) can then be saved > and attached to emails and Jira tickets to help evaluate the Geode cluster > status. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-2282) Provide ability to sort field while creating pdxType for jSON document(Need to document system property)
[ https://issues.apache.org/jira/browse/GEODE-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joey McAllister updated GEODE-2282: --- Assignee: (was: Joey McAllister) > Provide ability to sort field while creating pdxType for jSON document(Need > to document system property) > > > Key: GEODE-2282 > URL: https://issues.apache.org/jira/browse/GEODE-2282 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Hitesh Khamesra > Fix For: 1.1.0 > > > There is the possibility that same JSON document can create multiple pdxType > ids, if different JSON docs contain same fields in different order. Thus sort > those field while creating the pdxType id. Introduce system property to > enable this feature. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-2353) Verify no clear-text passwords in documentation
Joey McAllister created GEODE-2353: -- Summary: Verify no clear-text passwords in documentation Key: GEODE-2353 URL: https://issues.apache.org/jira/browse/GEODE-2353 Project: Geode Issue Type: Sub-task Components: docs Reporter: Joey McAllister Fix For: 1.1.0 Find locations in the manual where notes were made that the password is recorded or available in clear text, and remove them. GEODE-2119 ticket fixed all of them. Passwords are no longer seen in clear text. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-2300) Document default names for start locator/server
[ https://issues.apache.org/jira/browse/GEODE-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joey McAllister updated GEODE-2300: --- Fix Version/s: 1.1.0 > Document default names for start locator/server > --- > > Key: GEODE-2300 > URL: https://issues.apache.org/jira/browse/GEODE-2300 > Project: Geode > Issue Type: Sub-task > Components: docs >Reporter: Joey McAllister > Fix For: 1.1.0 > > > Documentation for GEODE-182 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-2300) Document default names for start locator/server
[ https://issues.apache.org/jira/browse/GEODE-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joey McAllister updated GEODE-2300: --- Issue Type: Sub-task (was: Task) Parent: GEODE-182 > Document default names for start locator/server > --- > > Key: GEODE-2300 > URL: https://issues.apache.org/jira/browse/GEODE-2300 > Project: Geode > Issue Type: Sub-task > Components: docs >Reporter: Joey McAllister > > Documentation for GEODE-182 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-2300) Document default names for start locator/server
Joey McAllister created GEODE-2300: -- Summary: Document default names for start locator/server Key: GEODE-2300 URL: https://issues.apache.org/jira/browse/GEODE-2300 Project: Geode Issue Type: Task Components: docs Reporter: Joey McAllister Documentation for GEODE-182 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-2031) Host documentation for releases
[ https://issues.apache.org/jira/browse/GEODE-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joey McAllister updated GEODE-2031: --- Priority: Minor (was: Major) > Host documentation for releases > --- > > Key: GEODE-2031 > URL: https://issues.apache.org/jira/browse/GEODE-2031 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Anthony Baker >Assignee: Joey McAllister >Priority: Minor > Fix For: 1.1.0 > > > Currently we overwrite documentation hosted on geode.apache.org with every > release. We should allow a user to browse the documentation (user guide + > javadocs) for past releases, not just the most recent release. > Improvement: > 1) The documentation page always points to the docs for the latest release. > 2) There is a documentation link associated with each release just like we do > release links for source and binary artifacts. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-2281) can not create redis server as the document describle
[ https://issues.apache.org/jira/browse/GEODE-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joey McAllister updated GEODE-2281: --- Component/s: docs > can not create redis server as the document describle > -- > > Key: GEODE-2281 > URL: https://issues.apache.org/jira/browse/GEODE-2281 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: netroby > > gfsh> start server --name=server1 --redis-bind-address=localhost > --redis-port=11211 --J=-Dgemfireredis.regiontype=PARTITION_PERSISTENT > Starting a Geode Server in > /home/huzhifeng/workspace/geode-demo/apache-geode-1.0.0-incubating/server1... > The Cache Server process terminated unexpectedly with exit status 1. Please > refer to the log file in > /home/huzhifeng/workspace/geode-demo/apache-geode-1.0.0-incubating/server1 > for full details. > Exception in thread "main" java.lang.RuntimeException: An IO error occurred > while starting a Server in > /home/huzhifeng/workspace/geode-demo/apache-geode-1.0.0-incubating/server1 on > 172.17.0.1[40404]: Network is unreachable; port (40404) is not available on > localhost. > at > org.apache.geode.distributed.ServerLauncher.start(ServerLauncher.java:735) > at > org.apache.geode.distributed.ServerLauncher.run(ServerLauncher.java:633) > at > org.apache.geode.distributed.ServerLauncher.main(ServerLauncher.java:184) > Caused by: java.net.BindException: Network is unreachable; port (40404) is > not available on localhost. > at > org.apache.geode.distributed.AbstractLauncher.assertPortAvailable(AbstractLauncher.java:127) > at > org.apache.geode.distributed.ServerLauncher.start(ServerLauncher.java:688) > ... 2 more > http://geode.apache.org/docs/guide/tools_modules/redis_adapter.html > I download the latest geode binary distribute -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-2256) Create Colocation Example
[
https://issues.apache.org/jira/browse/GEODE-2256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joey McAllister updated GEODE-2256:
---
Priority: Minor (was: Major)
> Create Colocation Example
> -
>
> Key: GEODE-2256
> URL: https://issues.apache.org/jira/browse/GEODE-2256
> Project: Geode
> Issue Type: New Feature
> Components: docs
>Reporter: Joey McAllister
>Priority: Minor
>
> Mike Stolz recommended on the Geode User list that "We should make a generic
> implementation of what Udo described here as part of the Geode examples. It's
> such a frequently used pattern."
> Here is the original request from Amit Pandey:
> {quote}
> I saw that in order to co locate different caches you can use
> "colocated-with" attribute.
> However how does Spring or Geode determine (based on which attributes ) that
> they will be collocated. Lets say two regions containing Customer and
> Account needs to be collocated. I want to use the accountPK present in both
> classes for collocation and not on other attributes which might have the same
> name (to give an artificial example lets say there is a "status" attribute
> which is Y in both but which I dont want to be used for determining
> collocation.
> {quote}
> And here is Udo's response:
> {quote}
> Colocation works by making sure that the same buckets are placed on the
> same server. It works in a parent-child relationship. Where RegionB is
> colocated with RegionA.
> For colocation to work you either need to use the same key or a
> PartitionResolver. A PartitionResolver is a custom impl that provides
> the mechanism, that determines what bucket each entry is put into, a way
> to make sure that entries for RegionB get the same bucket as the
> colocated entry in RegionA.
> Be very careful that the PartitionResolver uses the key only and not the
> value.
> In your case I'm sure that an Account would have reference to its
> parent, the customer. So I would use the customerKey for the colocation.
> Remember that keys can be "complex". i.e Have an accountID and a
> customerID. If you make the complex object have it's hashCode and equals
> point at the accountID then it will behave the same way as you would if
> you only used the accountID. Then, with the customerID being present in
> the complex accountID, you could then have a partitionResolver on the
> the Accounts region that would return the customerID (which would then
> be the same key that you used for the customer in your Customer region).
> Which means any account that is entered will be colocated with its
> customer information.
> In short, if you make sure that the mechanism that determines the bucket
> number always returns the same bucket number for colocated objects,
> related data will be stored on the same server.
> http://geode.apache.org/docs/guide/developing/partitioned_regions/using_custom_partition_resolvers.html
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (GEODE-2256) Create Colocation Example
Joey McAllister created GEODE-2256:
--
Summary: Create Colocation Example
Key: GEODE-2256
URL: https://issues.apache.org/jira/browse/GEODE-2256
Project: Geode
Issue Type: New Feature
Components: docs
Reporter: Joey McAllister
Mike Stolz recommended on the Geode User list that "We should make a generic
implementation of what Udo described here as part of the Geode examples. It's
such a frequently used pattern."
Here is the original request from Amit Pandey:
{quote}
I saw that in order to co locate different caches you can use "colocated-with"
attribute.
However how does Spring or Geode determine (based on which attributes ) that
they will be collocated. Lets say two regions containing Customer and Account
needs to be collocated. I want to use the accountPK present in both classes for
collocation and not on other attributes which might have the same name (to give
an artificial example lets say there is a "status" attribute which is Y in both
but which I dont want to be used for determining collocation.
{quote}
And here is Udo's response:
{quote}
Colocation works by making sure that the same buckets are placed on the
same server. It works in a parent-child relationship. Where RegionB is
colocated with RegionA.
For colocation to work you either need to use the same key or a
PartitionResolver. A PartitionResolver is a custom impl that provides
the mechanism, that determines what bucket each entry is put into, a way
to make sure that entries for RegionB get the same bucket as the
colocated entry in RegionA.
Be very careful that the PartitionResolver uses the key only and not the
value.
In your case I'm sure that an Account would have reference to its
parent, the customer. So I would use the customerKey for the colocation.
Remember that keys can be "complex". i.e Have an accountID and a
customerID. If you make the complex object have it's hashCode and equals
point at the accountID then it will behave the same way as you would if
you only used the accountID. Then, with the customerID being present in
the complex accountID, you could then have a partitionResolver on the
the Accounts region that would return the customerID (which would then
be the same key that you used for the customer in your Customer region).
Which means any account that is entered will be colocated with its
customer information.
In short, if you make sure that the mechanism that determines the bucket
number always returns the same bucket number for colocated objects,
related data will be stored on the same server.
http://geode.apache.org/docs/guide/developing/partitioned_regions/using_custom_partition_resolvers.html
{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (GEODE-2134) Doc update of schema location
[
https://issues.apache.org/jira/browse/GEODE-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joey McAllister resolved GEODE-2134.
Resolution: Duplicate
Fix Version/s: 1.1.0
Resolved in GEODE-2135 (https://issues.apache.org/jira/browse/GEODE-2135)
> Doc update of schema location
> --
>
> Key: GEODE-2134
> URL: https://issues.apache.org/jira/browse/GEODE-2134
> Project: Geode
> Issue Type: Bug
> Components: docs
>Reporter: Karen Smoler Miller
> Fix For: 1.1.0
>
>
> Throughout the documentation, update the schema location to be
> {{http://geode.apache.org/schema/cache/cache-1.0.xsd}}
> Incorrect location uses {{geode.incubator.apache.org}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-2138) gfsh 'start' reports 'GemFire Version'
[ https://issues.apache.org/jira/browse/GEODE-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joey McAllister updated GEODE-2138: --- Component/s: (was: docs) > gfsh 'start' reports 'GemFire Version' > -- > > Key: GEODE-2138 > URL: https://issues.apache.org/jira/browse/GEODE-2138 > Project: Geode > Issue Type: Bug > Components: gfsh >Reporter: Dave Barnes >Assignee: Nilkanth Patel >Priority: Minor > > The gfsh 'start locator' and 'start server' commands report 'GemFire version' > followed by a Geode version string. For example: > $ start locator --name=locator1 > Starting a Geode Locator in /Users/dbarnes/my_geode/locator1... > ... > Locator in /Users/dbarnes/my_geode/locator1 on 192.168.1.80[10334] as > locator1 is currently online. > Process ID: 1327 > Uptime: 4 seconds > GemFire Version: 1.1.0-SNAPSHOT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-536) Remove i18n code
[ https://issues.apache.org/jira/browse/GEODE-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783357#comment-15783357 ] Joey McAllister commented on GEODE-536: --- Found no "i18n" references in user guide, and so removed `docs` component. > Remove i18n code > > > Key: GEODE-536 > URL: https://issues.apache.org/jira/browse/GEODE-536 > Project: Geode > Issue Type: Task > Components: logging >Reporter: Roman Shtykh >Priority: Minor > > i18n is not needed. No plans to support it so far. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-536) Remove i18n code
[ https://issues.apache.org/jira/browse/GEODE-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joey McAllister updated GEODE-536: -- Component/s: (was: docs) > Remove i18n code > > > Key: GEODE-536 > URL: https://issues.apache.org/jira/browse/GEODE-536 > Project: Geode > Issue Type: Task > Components: logging >Reporter: Roman Shtykh >Priority: Minor > > i18n is not needed. No plans to support it so far. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
