[jira] [Created] (GEODE-2976) gfsh 'export cluster-config' behavior does not match online help
Dave Barnes created GEODE-2976: -- Summary: gfsh 'export cluster-config' behavior does not match online help Key: GEODE-2976 URL: https://issues.apache.org/jira/browse/GEODE-2976 Project: Geode Issue Type: Bug Components: docs, gfsh Reporter: Dave Barnes [Geode v1.1] Online help and userman docs for gfsh 'export cluster-config' specify two options that work together, --zip-file-name and --dir (shown below). In practice, I found that --dir is ignored and --zip-file-name must be a fully-qualified path. FWIW, the manual shows one example of each (cluster tutorial vs gfsh reference). Unsuccessful command: gfsh>export cluster-configuration --zip-file-name=myClusterConfig.zip --dir=/Users/dbarnes Could not process command due to GemFire error. Error while processing command Reason : null Successful command: gfsh>export cluster-configuration --zip-file-name=/Users/dbarnes/myClusterConfig.zip Downloading cluster configuration : /Users/dbarnes/myClusterConfig.zip Online help: gfsh>help export cluster-configuration NAME export cluster-configuration IS AVAILABLE true SYNOPSIS Exports the cluster configuration artifacts as a zip file. SYNTAX export cluster-configuration --zip-file-name=value [--dir=value] PARAMETERS zip-file-name Name of the zip file containing the exported cluster configuration artifacts Required: true dir The directory in which the exported cluster configuration artifacts will be saved Required: false -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (GEODE-2974) Geode throws GemFire error
Dave Barnes created GEODE-2974: -- Summary: 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 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] [Assigned] (GEODE-2941) Pulse documentation is outdated
[ https://issues.apache.org/jira/browse/GEODE-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-2941: -- Assignee: Dave Barnes > 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] [Resolved] (GEODE-2728) Client quickstarts: CMake for security fails to build library
[ https://issues.apache.org/jira/browse/GEODE-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-2728. Resolution: Fixed Fix Version/s: 1.2.0 Security quickstart examples removed from code & docs. > Client quickstarts: CMake for security fails to build library > - > > Key: GEODE-2728 > URL: https://issues.apache.org/jira/browse/GEODE-2728 > Project: Geode > Issue Type: Bug > Components: docs, native client >Reporter: Dave Barnes > Fix For: 1.2.0 > > > In the geode-native client distribution, the CMake code for building the > security library fails in a couple of ways. Symptoms: > - CMake still relies on finding $GFCPP in the environment and complains if > it's not found. > - CMake will install only to /lib, ignoring CMAKE_INSTALL_PREFIX if it is > specified on the command line. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (GEODE-2815) Incorrect Error Message in REST API docs for {region}/{key} HTTP.GET command
[
https://issues.apache.org/jira/browse/GEODE-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Barnes resolved GEODE-2815.
Resolution: Fixed
Fix Version/s: 1.2.0
> Incorrect Error Message in REST API docs for {region}/{key} HTTP.GET command
>
>
> Key: GEODE-2815
> URL: https://issues.apache.org/jira/browse/GEODE-2815
> Project: Geode
> Issue Type: Bug
> Components: docs
>Affects Versions: 1.1.1, 1.2.0
>Reporter: Michael Martell
>Assignee: Dave Barnes
>Priority: Minor
> Fix For: 1.2.0
>
>
> According to the docs at
> http://gemfire.docs.pivotal.io/geode/rest_apps/get_region_key_data.html error
> responses HTTP 400 and HTTP 404 appear to be very similar,
> # 400 - BAD REQUEST - Returned if the supplied key is not found in the region.
> # 404 - NOT FOUND - Returned if key does not exist for the region.
> The source code at PdxBasedCrudController.java:210 & 213 show that 404
> actually means "Region does not exist", thus the documentation appears to be
> incorrect. Other commands are correct in the docs showing 404 means region
> does not exist.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (GEODE-2352) Document that REST API requires two properties
[ https://issues.apache.org/jira/browse/GEODE-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-2352. Resolution: Fixed Fix Version/s: 1.2.0 > Document that REST API requires two properties > -- > > Key: GEODE-2352 > URL: https://issues.apache.org/jira/browse/GEODE-2352 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes > Fix For: 1.2.0 > > > Pulkit Chandra wrote in GEODE-2052: > The REST api needs bind address property and http-service-port. Its not > called out clearly in the docs that they are *mandatory*. > [link to docs > section](http://geode.incubator.apache.org/docs/guide/rest_apps/setup_config.html) > quote > ``` > To enable the developer REST API service in Apache Geode, set the > start-dev-rest-api Geode property to true when starting a data node using > either gfsh or the ServerLauncher API. Setting this property to true on a > data node will start up an embedded Jetty server and deploy the REST > developer API WAR file. > ``` > We also found out that some of the gemfire.properties do not get applied when > supplied in geode.properties but rather have to be passed as command line > properties. e.g. enabling rest api. > It would be nice to call that out clearly in docs. > It should highlight that its necessary to have 2 more properties bind-address > and http-service-port defined to make it work. > We would be happy to provide further details on this matter if needed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (GEODE-2613) Incorrect security privilege listed for 'execute function'
[ https://issues.apache.org/jira/browse/GEODE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-2613. Resolution: Duplicate Same as GEODE-2830 > Incorrect security privilege listed for 'execute function' > -- > > Key: GEODE-2613 > URL: https://issues.apache.org/jira/browse/GEODE-2613 > Project: Geode > Issue Type: Bug > Components: docs, security >Reporter: Diane Hardman >Assignee: Dave Barnes > > Under 'Implementing Authorization" are 2 tables; one for client operations > and another for general gfsh commands. 'execute function' is listed in both > tables but with different privilege requirements. > The correct privilege required is DATA:WRITE for 'execute function' in either > context. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (GEODE-2613) Incorrect security privilege listed for 'execute function'
[ https://issues.apache.org/jira/browse/GEODE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-2613: -- Assignee: Dave Barnes > Incorrect security privilege listed for 'execute function' > -- > > Key: GEODE-2613 > URL: https://issues.apache.org/jira/browse/GEODE-2613 > Project: Geode > Issue Type: Bug > Components: docs, security >Reporter: Diane Hardman >Assignee: Dave Barnes > > Under 'Implementing Authorization" are 2 tables; one for client operations > and another for general gfsh commands. 'execute function' is listed in both > tables but with different privilege requirements. > The correct privilege required is DATA:WRITE for 'execute function' in either > context. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (GEODE-2888) user guide: REST API Region Endpoints use 'gemfire-api' in their names
Dave Barnes created GEODE-2888: -- Summary: user guide: REST API Region Endpoints use 'gemfire-api' in their names Key: GEODE-2888 URL: https://issues.apache.org/jira/browse/GEODE-2888 Project: Geode Issue Type: Improvement Components: docs Reporter: Dave Barnes The name 'gemfire-api' should be replaced by 'geode' in the Region Endpoints section of the manual. See http://geode.apache.org/docs/guide/11/rest_apps/rest_regions.html and its subsections. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2815) Incorrect Error Message in REST API docs for {region}/{key} HTTP.GET command
[
https://issues.apache.org/jira/browse/GEODE-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15999101#comment-15999101
]
Dave Barnes commented on GEODE-2815:
Digging a bit deeper, 404 does mean 'not found', and in the REST API context it
can mean 'Region not found', 'Key not found' or 'Either key or region not
found', depending on what was being requested.
Edited the various REST API command docs accordingly.
> Incorrect Error Message in REST API docs for {region}/{key} HTTP.GET command
>
>
> Key: GEODE-2815
> URL: https://issues.apache.org/jira/browse/GEODE-2815
> Project: Geode
> Issue Type: Bug
> Components: docs
>Affects Versions: 1.1.1, 1.2.0
>Reporter: Michael Martell
>Assignee: Dave Barnes
>Priority: Minor
>
> According to the docs at
> http://gemfire.docs.pivotal.io/geode/rest_apps/get_region_key_data.html error
> responses HTTP 400 and HTTP 404 appear to be very similar,
> # 400 - BAD REQUEST - Returned if the supplied key is not found in the region.
> # 404 - NOT FOUND - Returned if key does not exist for the region.
> The source code at PdxBasedCrudController.java:210 & 213 show that 404
> actually means "Region does not exist", thus the documentation appears to be
> incorrect. Other commands are correct in the docs showing 404 means region
> does not exist.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (GEODE-1996) There are confusing references to "multicast" for locators ports
[ https://issues.apache.org/jira/browse/GEODE-1996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-1996. Resolution: Fixed Fix Version/s: 1.2.0 > There are confusing references to "multicast" for locators ports > > > Key: GEODE-1996 > URL: https://issues.apache.org/jira/browse/GEODE-1996 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Udo Kohlmeyer >Assignee: Dave Barnes > Fix For: 1.2.0 > > > The documentation seems to contain confusing terms when it comes to locators > and locators ports. In the documentation, we state that port the locator runs > on as a *multicast* port. This is incorrect as the multicast port is > configured by the property `mcast-port`. > http://geode.apache.org/docs/guide/11/configuring/running/firewalls_ports.html > - mentions ??By default, if not otherwise specified, Geode locators use the > default multicast port 10334.?? > We might have to scour the documentation for the term multicast and validate > that this is the correct usage for that scenario -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (GEODE-2815) Incorrect Error Message in REST API docs for {region}/{key} HTTP.GET command
[
https://issues.apache.org/jira/browse/GEODE-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Barnes reassigned GEODE-2815:
--
Assignee: Dave Barnes
> Incorrect Error Message in REST API docs for {region}/{key} HTTP.GET command
>
>
> Key: GEODE-2815
> URL: https://issues.apache.org/jira/browse/GEODE-2815
> Project: Geode
> Issue Type: Bug
> Components: docs
>Affects Versions: 1.1.1, 1.2.0
>Reporter: Michael Martell
>Assignee: Dave Barnes
>Priority: Minor
>
> According to the docs at
> http://gemfire.docs.pivotal.io/geode/rest_apps/get_region_key_data.html error
> responses HTTP 400 and HTTP 404 appear to be very similar,
> # 400 - BAD REQUEST - Returned if the supplied key is not found in the region.
> # 404 - NOT FOUND - Returned if key does not exist for the region.
> The source code at PdxBasedCrudController.java:210 & 213 show that 404
> actually means "Region does not exist", thus the documentation appears to be
> incorrect. Other commands are correct in the docs showing 404 means region
> does not exist.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (GEODE-1996) There are confusing references to "multicast" for locators ports
[ https://issues.apache.org/jira/browse/GEODE-1996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes updated GEODE-1996: --- Description: The documentation seems to contain confusing terms when it comes to locators and locators ports. In the documentation, we state that port the locator runs on as a *multicast* port. This is incorrect as the multicast port is configured by the property `mcast-port`. http://geode.apache.org/docs/guide/11/configuring/running/firewalls_ports.html - mentions ??By default, if not otherwise specified, Geode locators use the default multicast port 10334.?? We might have to scour the documentation for the term multicast and validate that this is the correct usage for that scenario was: The documentation seems to contain confusing terms when it comes to locators and locators ports. In the documentation, we state that port the locator runs on as a *multicast* port. This is incorrect as the multicast port is configured by the property `mcast-port`. http://geode.docs.pivotal.io/docs/configuring/running/firewalls_ports.html - mentions ??By default, if not otherwise specified, Geode locators use the default multicast port 10334.?? We might have to scour the documentation for the term multicast and validate that this is the correct usage for that scenario > There are confusing references to "multicast" for locators ports > > > Key: GEODE-1996 > URL: https://issues.apache.org/jira/browse/GEODE-1996 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Udo Kohlmeyer >Assignee: Dave Barnes > > The documentation seems to contain confusing terms when it comes to locators > and locators ports. In the documentation, we state that port the locator runs > on as a *multicast* port. This is incorrect as the multicast port is > configured by the property `mcast-port`. > http://geode.apache.org/docs/guide/11/configuring/running/firewalls_ports.html > - mentions ??By default, if not otherwise specified, Geode locators use the > default multicast port 10334.?? > We might have to scour the documentation for the term multicast and validate > that this is the correct usage for that scenario -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (GEODE-2830) Required permission for executing a function should be DATA:WRITE
[ https://issues.apache.org/jira/browse/GEODE-2830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-2830. Resolution: Fixed Fix Version/s: 1.2.0 > Required permission for executing a function should be DATA:WRITE > - > > Key: GEODE-2830 > URL: https://issues.apache.org/jira/browse/GEODE-2830 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Diane Hardman >Assignee: Dave Barnes > Fix For: 1.2.0 > > > The required permission for executing a function as listed in the gfsh > command table (2nd table) is wrong in the docs: > http://gemfire.docs.pivotal.io/geode/managing/security/implementing_authorization.html > It is listed as DATA:MANAGE in the gfsh command table, but should be > DATA:WRITE. > The correct permission is listed in the client operation table above the gfsh > table. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (GEODE-2843) User Guide - example should specify
[ https://issues.apache.org/jira/browse/GEODE-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-2843. Resolution: Fixed Fix Version/s: 1.2.0 Fixed several occurrences on the client-cache reference page. > User Guide - example should specify > -- > > Key: GEODE-2843 > URL: https://issues.apache.org/jira/browse/GEODE-2843 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes > Fix For: 1.2.0 > > > Excerpt from John Blum's response to a user's question: > See the example here: > http://geode.apache.org/docs/guide/11/reference/topics/client-cache.html#cc-pdx > Unfortunately, the example is WRONG, as it is using the "peer" cache element > tag ( instead of ), but this reference ([5]) is from > client-cache section... -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (GEODE-2778) gfsh help now uses log4j log levels: update user guide
[ https://issues.apache.org/jira/browse/GEODE-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-2778. Resolution: Fixed > gfsh help now uses log4j log levels: update user guide > -- > > Key: GEODE-2778 > URL: https://issues.apache.org/jira/browse/GEODE-2778 > Project: Geode > Issue Type: Sub-task > Components: docs, gfsh >Reporter: Dave Barnes >Assignee: Dave Barnes > Fix For: 1.2.0 > > > Update the user guide to reflect this change. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (GEODE-1996) There are confusing references to "multicast" for locators ports
[ https://issues.apache.org/jira/browse/GEODE-1996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-1996: -- Assignee: Dave Barnes > There are confusing references to "multicast" for locators ports > > > Key: GEODE-1996 > URL: https://issues.apache.org/jira/browse/GEODE-1996 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Udo Kohlmeyer >Assignee: Dave Barnes > > The documentation seems to contain confusing terms when it comes to locators > and locators ports. In the documentation, we state that port the locator runs > on as a *multicast* port. This is incorrect as the multicast port is > configured by the property `mcast-port`. > http://geode.docs.pivotal.io/docs/configuring/running/firewalls_ports.html - > mentions ??By default, if not otherwise specified, Geode locators use the > default multicast port 10334.?? > We might have to scour the documentation for the term multicast and validate > that this is the correct usage for that scenario -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (GEODE-2830) Required permission for executing a function should be DATA:WRITE
[ https://issues.apache.org/jira/browse/GEODE-2830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-2830: -- Assignee: Dave Barnes > Required permission for executing a function should be DATA:WRITE > - > > Key: GEODE-2830 > URL: https://issues.apache.org/jira/browse/GEODE-2830 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Diane Hardman >Assignee: Dave Barnes > > The required permission for executing a function as listed in the gfsh > command table (2nd table) is wrong in the docs: > http://gemfire.docs.pivotal.io/geode/managing/security/implementing_authorization.html > It is listed as DATA:MANAGE in the gfsh command table, but should be > DATA:WRITE. > The correct permission is listed in the client operation table above the gfsh > table. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (GEODE-2843) User Guide - example should specify
[ https://issues.apache.org/jira/browse/GEODE-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-2843: -- Assignee: Dave Barnes > User Guide - example should specify > -- > > Key: GEODE-2843 > URL: https://issues.apache.org/jira/browse/GEODE-2843 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes > > Excerpt from John Blum's response to a user's question: > See the example here: > http://geode.apache.org/docs/guide/11/reference/topics/client-cache.html#cc-pdx > Unfortunately, the example is WRONG, as it is using the "peer" cache element > tag ( instead of ), but this reference ([5]) is from > client-cache section... -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (GEODE-2850) gfsh commands accepting log level options use inconsistent syntax
[ https://issues.apache.org/jira/browse/GEODE-2850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-2850: -- Assignee: Kirk Lund > gfsh commands accepting log level options use inconsistent syntax > - > > Key: GEODE-2850 > URL: https://issues.apache.org/jira/browse/GEODE-2850 > Project: Geode > Issue Type: Bug > Components: docs, gfsh >Reporter: Dave Barnes >Assignee: Kirk Lund > > Some gfsh commands accept "--loglevel", others require "--log-level". > For example, > "change loglevel" insists on --loglevel=value > "start server" seems to accept both --loglevel and --log-level -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (GEODE-2843) User Guide - example should specify
Dave Barnes created GEODE-2843: -- Summary: User Guide - example should specify Key: GEODE-2843 URL: https://issues.apache.org/jira/browse/GEODE-2843 Project: Geode Issue Type: Bug Components: docs Reporter: Dave Barnes Excerpt from John Blum's response to a user's question: See the example here: http://geode.apache.org/docs/guide/11/reference/topics/client-cache.html#cc-pdx Unfortunately, the example is WRONG, as it is using the "peer" cache element tag ( instead of ), but this reference ([5]) is from client-cache section... -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (GEODE-2813) Incorrect Error Message for REST API, Doc Doesn
[ https://issues.apache.org/jira/browse/GEODE-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-2813. Resolution: Duplicate Duplicate of GEODE-2815. > Incorrect Error Message for REST API, Doc Doesn > --- > > Key: GEODE-2813 > URL: https://issues.apache.org/jira/browse/GEODE-2813 > Project: Geode > Issue Type: Bug >Reporter: Michael Martell > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (GEODE-2813) Incorrect Error Message for REST API, Doc Doesn
[ https://issues.apache.org/jira/browse/GEODE-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes closed GEODE-2813. -- > Incorrect Error Message for REST API, Doc Doesn > --- > > Key: GEODE-2813 > URL: https://issues.apache.org/jira/browse/GEODE-2813 > Project: Geode > Issue Type: Bug >Reporter: Michael Martell > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (GEODE-2780) Typo in client CONTRIBUTING.md file CMake 4.3 should be CMake 3.4
[ https://issues.apache.org/jira/browse/GEODE-2780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-2780. Resolution: Fixed Fix Version/s: 1.2.0 > Typo in client CONTRIBUTING.md file CMake 4.3 should be CMake 3.4 > - > > Key: GEODE-2780 > URL: https://issues.apache.org/jira/browse/GEODE-2780 > Project: Geode > Issue Type: Bug > Components: docs, native client >Reporter: Amey Barve >Assignee: Amey Barve > Fix For: 1.2.0 > > > There is typo in client CONTRIBUTING.md file CMake 4.3 should be CMake 3.4 > ### Required Tools > * [CMake 4.3](https://cmake.org/) or newer > There is no version 4.3 of CMake -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (GEODE-2710) Geode client docs: Update QuickStarts section
[ https://issues.apache.org/jira/browse/GEODE-2710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-2710. Resolution: Fixed Fix Version/s: 1.2.0 Docs match implementation to the extent possible at this time. > Geode client docs: Update QuickStarts section > - > > Key: GEODE-2710 > URL: https://issues.apache.org/jira/browse/GEODE-2710 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes > Fix For: 1.2.0 > > > Update the QuickStarts section to encompass (at least) two recent changes: > (1) Client examples were moved from their own directory in the codebase into > the QuickStarts. > (2) Manual text was 'rebranded' from proprietary to open-source, so > environment variables and other terminology need to change accordingly. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (GEODE-2826) Client docs - Delta Propagation API, correct .NET namespace notation
[ https://issues.apache.org/jira/browse/GEODE-2826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes updated GEODE-2826: --- Description: Reported by [~karensmolermiller]: file delta-propagation/delta-propagation-api.html The namespaces shown for .NET should be separated by a period (.), not two colons "::". was: Reported by [~karensmolermiller]: file delta-propagation/delta-propagation-api.html The namespaces shown for .NET should be separated by a period (.), not two colons "(::)". > Client docs - Delta Propagation API, correct .NET namespace notation > > > Key: GEODE-2826 > URL: https://issues.apache.org/jira/browse/GEODE-2826 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Minor > > Reported by [~karensmolermiller]: > file delta-propagation/delta-propagation-api.html > The namespaces shown for .NET should be separated by a period (.), not two > colons "::". -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (GEODE-2826) Client docs - Delta Propagation API, correct .NET namespace notation
[ https://issues.apache.org/jira/browse/GEODE-2826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes updated GEODE-2826: --- Description: Reported by [~karensmolermiller]: file delta-propagation/delta-propagation-api.html The namespaces shown for .NET should be separated by a period (.), not two colons "(::)". was: Reported by [~karensmolermiller]: file delta-propagation/delta-propagation-api.html The namespaces shown for .NET should be separated by a period (.), not two colons (::). > Client docs - Delta Propagation API, correct .NET namespace notation > > > Key: GEODE-2826 > URL: https://issues.apache.org/jira/browse/GEODE-2826 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Minor > > Reported by [~karensmolermiller]: > file delta-propagation/delta-propagation-api.html > The namespaces shown for .NET should be separated by a period (.), not two > colons "(::)". -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (GEODE-2826) Client docs - Delta Propagation API, correct .NET namespace notation
[ https://issues.apache.org/jira/browse/GEODE-2826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes updated GEODE-2826: --- Priority: Minor (was: Major) > Client docs - Delta Propagation API, correct .NET namespace notation > > > Key: GEODE-2826 > URL: https://issues.apache.org/jira/browse/GEODE-2826 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Dave Barnes >Priority: Minor > > Reported by [~karensmolermiller]: > file delta-propagation/delta-propagation-api.html > The namespaces shown for .NET should be separated by a period (.), not two > colons (::). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (GEODE-2826) Client docs - Delta Propagation API, correct .NET namespace notation
[ https://issues.apache.org/jira/browse/GEODE-2826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-2826: -- Assignee: Dave Barnes > Client docs - Delta Propagation API, correct .NET namespace notation > > > Key: GEODE-2826 > URL: https://issues.apache.org/jira/browse/GEODE-2826 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Minor > > Reported by [~karensmolermiller]: > file delta-propagation/delta-propagation-api.html > The namespaces shown for .NET should be separated by a period (.), not two > colons (::). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (GEODE-2826) Client docs - Delta Propagation API, correct .NET namespace notation
Dave Barnes created GEODE-2826: -- Summary: Client docs - Delta Propagation API, correct .NET namespace notation Key: GEODE-2826 URL: https://issues.apache.org/jira/browse/GEODE-2826 Project: Geode Issue Type: Bug Components: docs Reporter: Dave Barnes Reported by [~karensmolermiller]: file delta-propagation/delta-propagation-api.html The namespaces shown for .NET should be separated by a period (.), not two colons (::). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (GEODE-2821) Geode User Guide: Add running heads with logo
Dave Barnes created GEODE-2821: -- Summary: Geode User Guide: Add running heads with logo Key: GEODE-2821 URL: https://issues.apache.org/jira/browse/GEODE-2821 Project: Geode Issue Type: Improvement Components: docs Reporter: Dave Barnes In the Geode User Guide, add running heads with the Geode logo as in the Client Guide. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (GEODE-2821) Geode User Guide: Add running heads with logo
[ https://issues.apache.org/jira/browse/GEODE-2821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-2821: -- Assignee: Dave Barnes > Geode User Guide: Add running heads with logo > - > > Key: GEODE-2821 > URL: https://issues.apache.org/jira/browse/GEODE-2821 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes > > In the Geode User Guide, add running heads with the Geode logo as in the > Client Guide. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (GEODE-2138) gfsh 'start' reports 'GemFire Version'
[ https://issues.apache.org/jira/browse/GEODE-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes closed GEODE-2138. -- Fixed Jan 2017. Time to close the JIRA ticket. > 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 > Fix For: 1.1.1 > > > 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.15#6346)
[jira] [Resolved] (GEODE-2138) gfsh 'start' reports 'GemFire Version'
[ https://issues.apache.org/jira/browse/GEODE-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-2138. Resolution: Fixed Fix Version/s: 1.1.1 > 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 > Fix For: 1.1.1 > > > 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.15#6346)
[jira] [Resolved] (GEODE-2809) Geode docs: Clarify SSL setup for client
[ https://issues.apache.org/jira/browse/GEODE-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-2809. Resolution: Fixed Fix Version/s: 1.2.0 > Geode docs: Clarify SSL setup for client > > > Key: GEODE-2809 > URL: https://issues.apache.org/jira/browse/GEODE-2809 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes > Fix For: 1.2.0 > > > The page managing/security/implementing_ssl.html contains an example of > setting ssl properties for a client. It would be helpful to clarify which > properties refer to client-local entities (e.g. path to keystore) and which > are local reflections of server settings (e.g. whether locators and servers > are ssl-enabled). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (GEODE-2809) Geode docs: Clarify SSL setup for client
[ https://issues.apache.org/jira/browse/GEODE-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-2809: -- Assignee: Dave Barnes > Geode docs: Clarify SSL setup for client > > > Key: GEODE-2809 > URL: https://issues.apache.org/jira/browse/GEODE-2809 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes > > The page managing/security/implementing_ssl.html contains an example of > setting ssl properties for a client. It would be helpful to clarify which > properties refer to client-local entities (e.g. path to keystore) and which > are local reflections of server settings (e.g. whether locators and servers > are ssl-enabled). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (GEODE-2809) Geode docs: Clarify SSL setup for client
Dave Barnes created GEODE-2809: -- Summary: Geode docs: Clarify SSL setup for client Key: GEODE-2809 URL: https://issues.apache.org/jira/browse/GEODE-2809 Project: Geode Issue Type: Improvement Components: docs Reporter: Dave Barnes The page managing/security/implementing_ssl.html contains an example of setting ssl properties for a client. It would be helpful to clarify which properties refer to client-local entities (e.g. path to keystore) and which are local reflections of server settings (e.g. whether locators and servers are ssl-enabled). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (GEODE-2784) Geode client docs: Cmake reqires the --config option when a generator is specified
[ https://issues.apache.org/jira/browse/GEODE-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes updated GEODE-2784: --- Fix Version/s: 1.2.0 > Geode client docs: Cmake reqires the --config option when a generator is > specified > -- > > Key: GEODE-2784 > URL: https://issues.apache.org/jira/browse/GEODE-2784 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes > Fix For: 1.2.0 > > > When generating for IDEs such as VisualStudio or Xcode, CMAKE_BUILD_TYPE is a > no-op on config step > and on the build step one MUST specify --config [Debug|Release]. For example: > cmake -G"Visual Studio 12 2013 Win64" c:\install\templates\security > -DGFCPP=c:\install > cmake --build . --config Release > cmake --build . --config Release --target install -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (GEODE-2784) Geode client docs: Cmake reqires the --config option when a generator is specified
[ https://issues.apache.org/jira/browse/GEODE-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-2784. Resolution: Fixed > Geode client docs: Cmake reqires the --config option when a generator is > specified > -- > > Key: GEODE-2784 > URL: https://issues.apache.org/jira/browse/GEODE-2784 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes > > When generating for IDEs such as VisualStudio or Xcode, CMAKE_BUILD_TYPE is a > no-op on config step > and on the build step one MUST specify --config [Debug|Release]. For example: > cmake -G"Visual Studio 12 2013 Win64" c:\install\templates\security > -DGFCPP=c:\install > cmake --build . --config Release > cmake --build . --config Release --target install -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2710) Geode client docs: Update QuickStarts section
[ https://issues.apache.org/jira/browse/GEODE-2710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15969591#comment-15969591 ] Dave Barnes commented on GEODE-2710: Updated cmake commands - WIP, more to do. > Geode client docs: Update QuickStarts section > - > > Key: GEODE-2710 > URL: https://issues.apache.org/jira/browse/GEODE-2710 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes > > Update the QuickStarts section to encompass (at least) two recent changes: > (1) Client examples were moved from their own directory in the codebase into > the QuickStarts. > (2) Manual text was 'rebranded' from proprietary to open-source, so > environment variables and other terminology need to change accordingly. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (GEODE-2784) Geode client docs: Cmake reqires the --config option when a generator is specified
Dave Barnes created GEODE-2784: -- Summary: Geode client docs: Cmake reqires the --config option when a generator is specified Key: GEODE-2784 URL: https://issues.apache.org/jira/browse/GEODE-2784 Project: Geode Issue Type: Improvement Components: docs Reporter: Dave Barnes When generating for IDEs such as VisualStudio or Xcode, CMAKE_BUILD_TYPE is a no-op on config step and on the build step one MUST specify --config [Debug|Release]. For example: cmake -G"Visual Studio 12 2013 Win64" c:\install\templates\security -DGFCPP=c:\install cmake --build . --config Release cmake --build . --config Release --target install -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (GEODE-2784) Geode client docs: Cmake reqires the --config option when a generator is specified
[ https://issues.apache.org/jira/browse/GEODE-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-2784: -- Assignee: Dave Barnes > Geode client docs: Cmake reqires the --config option when a generator is > specified > -- > > Key: GEODE-2784 > URL: https://issues.apache.org/jira/browse/GEODE-2784 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes > > When generating for IDEs such as VisualStudio or Xcode, CMAKE_BUILD_TYPE is a > no-op on config step > and on the build step one MUST specify --config [Debug|Release]. For example: > cmake -G"Visual Studio 12 2013 Win64" c:\install\templates\security > -DGFCPP=c:\install > cmake --build . --config Release > cmake --build . --config Release --target install -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (GEODE-2778) gfsh help now uses log4j log levels: update user guide
Dave Barnes created GEODE-2778: -- Summary: gfsh help now uses log4j log levels: update user guide Key: GEODE-2778 URL: https://issues.apache.org/jira/browse/GEODE-2778 Project: Geode Issue Type: Sub-task Reporter: Dave Barnes Update the user guide to reflect this change. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (GEODE-2778) gfsh help now uses log4j log levels: update user guide
[ https://issues.apache.org/jira/browse/GEODE-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes updated GEODE-2778: --- Component/s: docs > gfsh help now uses log4j log levels: update user guide > -- > > Key: GEODE-2778 > URL: https://issues.apache.org/jira/browse/GEODE-2778 > Project: Geode > Issue Type: Sub-task > Components: docs, gfsh >Reporter: Dave Barnes > Fix For: 1.2.0 > > > Update the user guide to reflect this change. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (GEODE-2778) gfsh help now uses log4j log levels: update user guide
[ https://issues.apache.org/jira/browse/GEODE-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-2778: -- Assignee: Dave Barnes > gfsh help now uses log4j log levels: update user guide > -- > > Key: GEODE-2778 > URL: https://issues.apache.org/jira/browse/GEODE-2778 > Project: Geode > Issue Type: Sub-task > Components: docs, gfsh >Reporter: Dave Barnes >Assignee: Dave Barnes > Fix For: 1.2.0 > > > Update the user guide to reflect this change. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (GEODE-2761) Docs: un-brand client cache plugin diagram
[ https://issues.apache.org/jira/browse/GEODE-2761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-2761. Resolution: Fixed > Docs: un-brand client cache plugin diagram > -- > > Key: GEODE-2761 > URL: https://issues.apache.org/jira/browse/GEODE-2761 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes > > For the native client, the figure referenced from within file > client-cache/application-plugins.html has labels that say "Native Client". > They should probably be redrawn to just say "Client". > The image is file `common/images/client-cache-plugins-run.gif` > The diagram is fairly simple. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (GEODE-2537) Docs: redraw image to remove GemFire label
[ https://issues.apache.org/jira/browse/GEODE-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-2537. Resolution: Fixed > Docs: redraw image to remove GemFire label > -- > > Key: GEODE-2537 > URL: https://issues.apache.org/jira/browse/GEODE-2537 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Karen Smoler Miller >Assignee: Dave Barnes > > The image referenced within the How Delta Propagation Works subsection of > *both* the Geode and the Geode Native manuals has labels that say 'GemFire.' > There do not appear to be any source files available, so this gif diagram > will need to be redrawn, and made available to both repos: geode and > geode-native. > The gif for the image is > - geode-native/docs/geode-native-docs/common/images/delta-propagation.gif > - geode/geode-docs/images/DeltaPropagation-1.gif -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (GEODE-2537) Docs: redraw image to remove GemFire label
[ https://issues.apache.org/jira/browse/GEODE-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-2537: -- Assignee: Dave Barnes > Docs: redraw image to remove GemFire label > -- > > Key: GEODE-2537 > URL: https://issues.apache.org/jira/browse/GEODE-2537 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Karen Smoler Miller >Assignee: Dave Barnes > > The image referenced within the How Delta Propagation Works subsection of > *both* the Geode and the Geode Native manuals has labels that say 'GemFire.' > There do not appear to be any source files available, so this gif diagram > will need to be redrawn, and made available to both repos: geode and > geode-native. > The gif for the image is > - geode-native/docs/geode-native-docs/common/images/delta-propagation.gif > - geode/geode-docs/images/DeltaPropagation-1.gif -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (GEODE-2761) Docs: un-brand client cache plugin diagram
[ https://issues.apache.org/jira/browse/GEODE-2761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-2761: -- Assignee: Dave Barnes > Docs: un-brand client cache plugin diagram > -- > > Key: GEODE-2761 > URL: https://issues.apache.org/jira/browse/GEODE-2761 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes > > For the native client, the figure referenced from within file > client-cache/application-plugins.html has labels that say "Native Client". > They should probably be redrawn to just say "Client". > The image is file `common/images/client-cache-plugins-run.gif` > The diagram is fairly simple. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (GEODE-2761) Docs: un-brand client cache plugin diagram
[ https://issues.apache.org/jira/browse/GEODE-2761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes updated GEODE-2761: --- Issue Type: Improvement (was: Bug) > Docs: un-brand client cache plugin diagram > -- > > Key: GEODE-2761 > URL: https://issues.apache.org/jira/browse/GEODE-2761 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes > > For the native client, the figure referenced from within file > client-cache/application-plugins.html has labels that say "Native Client". > They should probably be redrawn to just say "Client". > The image is file `common/images/client-cache-plugins-run.gif` > The diagram is fairly simple. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (GEODE-2761) Docs: un-brand client cache plugin diagram
Dave Barnes created GEODE-2761: -- Summary: Docs: un-brand client cache plugin diagram Key: GEODE-2761 URL: https://issues.apache.org/jira/browse/GEODE-2761 Project: Geode Issue Type: Bug Components: docs Reporter: Dave Barnes For the native client, the figure referenced from within file client-cache/application-plugins.html has labels that say "Native Client". They should probably be redrawn to just say "Client". The image is file `common/images/client-cache-plugins-run.gif` The diagram is fairly simple. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (GEODE-2581) New Client/Server Protocol Design Proposal
[ https://issues.apache.org/jira/browse/GEODE-2581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes updated GEODE-2581: --- Description: The goal here is to create a high-level design document that outlines the foundational design choices of the new protocol. As part of this story, we should have a document that describes the basics of writing a new client using the new client/server protocol. was: The goal here is the create a high-level design document that outlines the foundational design choices of the new protocol. As part of this story, we should have a document that describes the basics of writing a new client using the new client/server protocol. > New Client/Server Protocol Design Proposal > -- > > Key: GEODE-2581 > URL: https://issues.apache.org/jira/browse/GEODE-2581 > Project: Geode > Issue Type: Sub-task > Components: messaging >Reporter: Addison > > The goal here is to create a high-level design document that outlines the > foundational design choices of the new protocol. > As part of this story, we should have a document that describes the basics of > writing a new client using the new client/server protocol. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (GEODE-2513) Geode Native docs: rebrand to match open-source software
[ https://issues.apache.org/jira/browse/GEODE-2513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-2513. Resolution: Fixed Fix Version/s: 1.2.0 Wholesale client doc conversion from proprietary to open source is complete. Address subsequent doc issues with new tickets. > Geode Native docs: rebrand to match open-source software > > > Key: GEODE-2513 > URL: https://issues.apache.org/jira/browse/GEODE-2513 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes > Fix For: 1.2.0 > > > The newly-contributed Geode Native doc sources contain some GemFire artifacts > that have been purged from the open-source code. Docs should be updated to > match. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (GEODE-2513) Geode Native docs: rebrand to match open-source software
[ https://issues.apache.org/jira/browse/GEODE-2513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-2513: -- Assignee: Dave Barnes > Geode Native docs: rebrand to match open-source software > > > Key: GEODE-2513 > URL: https://issues.apache.org/jira/browse/GEODE-2513 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes > > The newly-contributed Geode Native doc sources contain some GemFire artifacts > that have been purged from the open-source code. Docs should be updated to > match. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (GEODE-2466) Document that examples were combined with quickstarts
[ https://issues.apache.org/jira/browse/GEODE-2466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes updated GEODE-2466: --- Fix Version/s: 1.2.0 > Document that examples were combined with quickstarts > - > > Key: GEODE-2466 > URL: https://issues.apache.org/jira/browse/GEODE-2466 > Project: Geode > Issue Type: Sub-task > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes > Fix For: 1.2.0 > > > See GEODE-2462 Unify Quckstarts and examples -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (GEODE-2466) Document that examples were combined with quickstarts
[ https://issues.apache.org/jira/browse/GEODE-2466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-2466. Resolution: Fixed Updated client documentation to reflect these changes. > Document that examples were combined with quickstarts > - > > Key: GEODE-2466 > URL: https://issues.apache.org/jira/browse/GEODE-2466 > Project: Geode > Issue Type: Sub-task > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes > > See GEODE-2462 Unify Quckstarts and examples -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (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 ] Dave Barnes resolved GEODE-2554. Resolution: Fixed Fix Version/s: 1.2.0 Old docs removed from the asf-site branch, only /10 and /11 remain. (No special measures taken to update third-party search engines, such as Google. Hoping their links to older Geode docs will time-out of their own accord.) > 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: Dave Barnes > 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] [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 ] Dave Barnes reassigned GEODE-2554: -- Assignee: Dave Barnes > 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: Dave Barnes > > 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] [Commented] (GEODE-2710) Geode client docs: Update QuickStarts section
[ https://issues.apache.org/jira/browse/GEODE-2710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15947932#comment-15947932 ] Dave Barnes commented on GEODE-2710: Made language changes. Encountered errors in the implementation. Filed a ticket on one problem (GEODE-2728), will create others as needed until docs describe a happy path to QuickStart success. > Geode client docs: Update QuickStarts section > - > > Key: GEODE-2710 > URL: https://issues.apache.org/jira/browse/GEODE-2710 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes > > Update the QuickStarts section to encompass (at least) two recent changes: > (1) Client examples were moved from their own directory in the codebase into > the QuickStarts. > (2) Manual text was 'rebranded' from proprietary to open-source, so > environment variables and other terminology need to change accordingly. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (GEODE-2728) Client quickstarts: CMake for security fails to build library
Dave Barnes created GEODE-2728: -- Summary: Client quickstarts: CMake for security fails to build library Key: GEODE-2728 URL: https://issues.apache.org/jira/browse/GEODE-2728 Project: Geode Issue Type: Bug Components: docs, native client Reporter: Dave Barnes In the geode-native client distribution, the CMake code for building the security library fails in a couple of ways. Symptoms: - CMake still relies on finding $GFCPP in the environment and complains if it's not found. - CMake will install only to /lib, ignoring CMAKE_INSTALL_PREFIX if it is specified on the command line. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (GEODE-2711) Geode Client docs: Rename and reorganize source files
Dave Barnes created GEODE-2711: -- Summary: Geode Client docs: Rename and reorganize source files Key: GEODE-2711 URL: https://issues.apache.org/jira/browse/GEODE-2711 Project: Geode Issue Type: Improvement Components: docs Reporter: Dave Barnes Client doc file contents have undergone a rebranding (GEODE-2513). Filenames themselves also need renaming to follow the new conventions. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (GEODE-2711) Geode Client docs: Rename and reorganize source files
[ https://issues.apache.org/jira/browse/GEODE-2711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-2711: -- Assignee: Dave Barnes > Geode Client docs: Rename and reorganize source files > - > > Key: GEODE-2711 > URL: https://issues.apache.org/jira/browse/GEODE-2711 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes > > Client doc file contents have undergone a rebranding (GEODE-2513). > Filenames themselves also need renaming to follow the new conventions. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (GEODE-2710) Geode client docs: Update QuickStarts section
Dave Barnes created GEODE-2710: -- Summary: Geode client docs: Update QuickStarts section Key: GEODE-2710 URL: https://issues.apache.org/jira/browse/GEODE-2710 Project: Geode Issue Type: Improvement Components: docs Reporter: Dave Barnes Update the QuickStarts section to encompass (at least) two recent changes: (1) Client examples were moved from their own directory in the codebase into the QuickStarts. (2) Manual text was 'rebranded' from proprietary to open-source, so environment variables and other terminology need to change accordingly. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (GEODE-2710) Geode client docs: Update QuickStarts section
[ https://issues.apache.org/jira/browse/GEODE-2710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-2710: -- Assignee: Dave Barnes > Geode client docs: Update QuickStarts section > - > > Key: GEODE-2710 > URL: https://issues.apache.org/jira/browse/GEODE-2710 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes > > Update the QuickStarts section to encompass (at least) two recent changes: > (1) Client examples were moved from their own directory in the codebase into > the QuickStarts. > (2) Manual text was 'rebranded' from proprietary to open-source, so > environment variables and other terminology need to change accordingly. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (GEODE-2379) Document new behavior of export logs
[ https://issues.apache.org/jira/browse/GEODE-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-2379. Resolution: Fixed Fix Version/s: 1.2.0 > Document new behavior of export logs > > > Key: GEODE-2379 > URL: https://issues.apache.org/jira/browse/GEODE-2379 > Project: Geode > Issue Type: Sub-task > Components: docs >Reporter: Joey McAllister >Assignee: Dave Barnes > Fix For: 1.2.0 > > > the new command help: > NAME > export logs > IS AVAILABLE > false > SYNOPSIS > Export the log files for a member or members. > SYNTAX > export logs [--dir=value] [--group=value(,value)*] > [--member=value(,value)*] [--log-level=value] [--only-log-level=value] > [--merge-log=value] [--start-time=value] [--end-time=value] > [--logs-only(=value)?] [--stats-only(=value)?] > PARAMETERS > dir > Local directory to which log files will be written. This is only used > when you are exporting logs using http connection. If not specified, user.dir > will be used. > Required: false > group > Group of members whose log files will be exported. > Required: false > member > Name/Id of the member whose log files will be exported. > Required: false > log-level > Minimum level of log entries to export. Valid values are: fatal, > error, warn, info, debug, trace and all. The default is "INFO". > Required: false > Default (if the parameter is not specified): INFO > only-log-level > Whether to only include those entries that exactly match the > --log-level specified. > Required: false > Default (if the parameter is not specified): false > merge-log > Whether to merge logs after exporting to the target directory. -- > deprecated > Required: false > Default (if the parameter is not specified): false > start-time > Log entries that occurred after this time will be exported. The > default is no limit. Format: /MM/dd/HH/mm/ss/SSS/z OR /MM/dd > Required: false > end-time > Log entries that occurred before this time will be exported. The > default is no limit. Format: /MM/dd/HH/mm/ss/SSS/z OR /MM/dd > Required: false > logs-only > Whether to only export logs > Required: false > Default (if the parameter is specified without value): true > Default (if the parameter is not specified): false > stats-only > Whether to only export statistics > Required: false > Default (if the parameter is specified without value): true > Default (if the parameter is not specified): false > changes are: --dir is not required anymore. added logs-only and stats-only > options. --merge-log is deprecated, group and member can be comma separated > strings. > Also note down in the docs: when this command is executed over jmx, the > exported logs will be saved as exportedlogs_xxx.zip in the connected > locator's working directory. If executed over http, the zip will be saved in > specified dir in the user's client machine. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (GEODE-2592) Document Lucene-related gfsh commands
[ https://issues.apache.org/jira/browse/GEODE-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-2592. Resolution: Fixed Fix Version/s: 1.2.0 > Document Lucene-related gfsh commands > - > > Key: GEODE-2592 > URL: https://issues.apache.org/jira/browse/GEODE-2592 > Project: Geode > Issue Type: New Feature > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes > Fix For: 1.2.0 > > > Add five new Lucene-related gfsh commands to the gfsh command reference pages: > create lucene index, describe lucene index, destroy lucene index, list lucene > indexes, search lucene. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (GEODE-2521) geode native docs: Document installation from source
[ https://issues.apache.org/jira/browse/GEODE-2521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes updated GEODE-2521: --- Fix Version/s: 1.2.0 > geode native docs: Document installation from source > > > Key: GEODE-2521 > URL: https://issues.apache.org/jira/browse/GEODE-2521 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes > Fix For: 1.2.0 > > > Update installation instructions to include building from source. Binary > distributions will also (presumably) be available on the website's Releases > page. (See the installation section of the Geode user manual for a model to > follow.) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (GEODE-2521) geode native docs: Document installation from source
[ https://issues.apache.org/jira/browse/GEODE-2521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-2521. Resolution: Fixed > geode native docs: Document installation from source > > > Key: GEODE-2521 > URL: https://issues.apache.org/jira/browse/GEODE-2521 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes > > Update installation instructions to include building from source. Binary > distributions will also (presumably) be available on the website's Releases > page. (See the installation section of the Geode user manual for a model to > follow.) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (GEODE-2664) all gfsh commands that contains log-level needs to be updated to use log4j levels
[ https://issues.apache.org/jira/browse/GEODE-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes updated GEODE-2664: --- Component/s: docs > all gfsh commands that contains log-level needs to be updated to use log4j > levels > - > > Key: GEODE-2664 > URL: https://issues.apache.org/jira/browse/GEODE-2664 > Project: Geode > Issue Type: Bug > Components: docs, gfsh >Reporter: Jinmei Liao > > The commands' auto completion are still giving user options with gemfire log > levels, but our logs are mostly using log4j now. We need to have these > commands accept log4j levels now. Here are the problems: > 1. "Export logs" command already accept log4j level, but the auto-complete > still hints users with gemfire levels, this is a must fix. > 2. The auto complete is also used by "start locator", "start server", "alter > config", "change log-level" commands, needs to update these commands to > accept log4j level as well. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (GEODE-2521) geode native docs: Document installation from source
[ https://issues.apache.org/jira/browse/GEODE-2521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-2521: -- Assignee: Dave Barnes > geode native docs: Document installation from source > > > Key: GEODE-2521 > URL: https://issues.apache.org/jira/browse/GEODE-2521 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes > > Update installation instructions to include building from source. Binary > distributions will also (presumably) be available on the website's Releases > page. (See the installation section of the Geode user manual for a model to > follow.) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (GEODE-2379) Document new behavior of export logs
[ https://issues.apache.org/jira/browse/GEODE-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-2379: -- Assignee: Dave Barnes > Document new behavior of export logs > > > Key: GEODE-2379 > URL: https://issues.apache.org/jira/browse/GEODE-2379 > Project: Geode > Issue Type: Sub-task > Components: docs >Reporter: Joey McAllister >Assignee: Dave Barnes > > the new command help: > NAME > export logs > IS AVAILABLE > false > SYNOPSIS > Export the log files for a member or members. > SYNTAX > export logs [--dir=value] [--group=value(,value)*] > [--member=value(,value)*] [--log-level=value] [--only-log-level=value] > [--merge-log=value] [--start-time=value] [--end-time=value] > [--logs-only(=value)?] [--stats-only(=value)?] > PARAMETERS > dir > Local directory to which log files will be written. This is only used > when you are exporting logs using http connection. If not specified, user.dir > will be used. > Required: false > group > Group of members whose log files will be exported. > Required: false > member > Name/Id of the member whose log files will be exported. > Required: false > log-level > Minimum level of log entries to export. Valid values are: fatal, > error, warn, info, debug, trace and all. The default is "INFO". > Required: false > Default (if the parameter is not specified): INFO > only-log-level > Whether to only include those entries that exactly match the > --log-level specified. > Required: false > Default (if the parameter is not specified): false > merge-log > Whether to merge logs after exporting to the target directory. -- > deprecated > Required: false > Default (if the parameter is not specified): false > start-time > Log entries that occurred after this time will be exported. The > default is no limit. Format: /MM/dd/HH/mm/ss/SSS/z OR /MM/dd > Required: false > end-time > Log entries that occurred before this time will be exported. The > default is no limit. Format: /MM/dd/HH/mm/ss/SSS/z OR /MM/dd > Required: false > logs-only > Whether to only export logs > Required: false > Default (if the parameter is specified without value): true > Default (if the parameter is not specified): false > stats-only > Whether to only export statistics > Required: false > Default (if the parameter is specified without value): true > Default (if the parameter is not specified): false > changes are: --dir is not required anymore. added logs-only and stats-only > options. --merge-log is deprecated, group and member can be comma separated > strings. > Also note down in the docs: when this command is executed over jmx, the > exported logs will be saved as exportedlogs_xxx.zip in the connected > locator's working directory. If executed over http, the zip will be saved in > specified dir in the user's client machine. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (GEODE-1195) Improve "Synchronizing Your Offline Disk Store with Your Cache" docs
[ https://issues.apache.org/jira/browse/GEODE-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-1195. Resolution: Fixed Fix Version/s: 1.2.0 > Improve "Synchronizing Your Offline Disk Store with Your Cache" docs > > > Key: GEODE-1195 > URL: https://issues.apache.org/jira/browse/GEODE-1195 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Darrel Schneider >Assignee: Dave Barnes > Fix For: 1.2.0 > > > The docs in question are: > http://geode.docs.pivotal.io/docs/managing/disk_storage/keeping_offline_disk_store_in_sync.html#syncing_offline_disk_store > Change "modify-disk-store" to "alter disk-store". Modify is the older command > and alter is the current gfsh command. > I think you should introduce this section with: > If you change or remove persistent regions by modifying your cache.xml or you > code that configures the regions then you should alter this disk-store to be > the same. If you don't then the next time this disk-store is recovered it > will recover all that regions data into a temporary region with the old > configuration. The old configuration will still consume the old configured > resources (heap memory, off-heap memory). If those resources are no longer > available (for example the old configuration of the region was off-heap but > you decide to no longer configure off-heap memory on the JVM) the disk-store > recovery will fail. So it is recommended that you change the stored > configuration to match the runtime configuration. > In the subsection on "Change Region Configuration" this list of things that > can be changed are out of date: > The disk store retains region capacity and load settings, including entry map > settings (initial capacity, concurrency level, load factor), LRU eviction > settings, and the statistics enabled boolean. > Instead of listing them all here and trying to keep that list up to date > perhaps it would be better to say: > The disk store retains a subset of the region configuration attributes (for a > list of the retained attributes see alter disk-store at > http://geode.docs.pivotal.io/docs/tools_modules/gfsh/command-pages/alter.html) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (GEODE-2603) Docs: geode-native user guide >> Security >> SSL setup needs update
[ https://issues.apache.org/jira/browse/GEODE-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-2603. Resolution: Fixed Fix Version/s: 1.2.0 > Docs: geode-native user guide >> Security >> SSL setup needs update > --- > > Key: GEODE-2603 > URL: https://issues.apache.org/jira/browse/GEODE-2603 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes > Fix For: 1.2.0 > > > Update SSL setup to refer to OpenSSL's own installation procedures. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (GEODE-2592) Document Lucene-related gfsh commands
[ https://issues.apache.org/jira/browse/GEODE-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes updated GEODE-2592: --- Description: Add five new Lucene-related gfsh commands to the gfsh command reference pages: create lucene index, describe lucene index, destroy lucene index, list lucene indexes, search lucene. was: Add four new Lucene-related gfsh commands to the gfsh command reference pages: create lucene index, describe lucene index, list lucene indexes, search lucene. > Document Lucene-related gfsh commands > - > > Key: GEODE-2592 > URL: https://issues.apache.org/jira/browse/GEODE-2592 > Project: Geode > Issue Type: New Feature > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes > > Add five new Lucene-related gfsh commands to the gfsh command reference pages: > create lucene index, describe lucene index, destroy lucene index, list lucene > indexes, search lucene. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (GEODE-2591) User guide: Lucene headings should be reflected in navigation pane
[ https://issues.apache.org/jira/browse/GEODE-2591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-2591. Resolution: Fixed Fix Version/s: 1.2.0 > User guide: Lucene headings should be reflected in navigation pane > -- > > Key: GEODE-2591 > URL: https://issues.apache.org/jira/browse/GEODE-2591 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Minor > Fix For: 1.2.0 > > > The left-hand subnav for the Lucene section of the user guide does not match > the topics in the text. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (GEODE-2603) Docs: geode-native user guide >> Security >> SSL setup needs update
Dave Barnes created GEODE-2603: -- Summary: Docs: geode-native user guide >> Security >> SSL setup needs update Key: GEODE-2603 URL: https://issues.apache.org/jira/browse/GEODE-2603 Project: Geode Issue Type: Improvement Components: docs Reporter: Dave Barnes Update SSL setup to refer to OpenSSL's own installation procedures. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (GEODE-2603) Docs: geode-native user guide >> Security >> SSL setup needs update
[ https://issues.apache.org/jira/browse/GEODE-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-2603: -- Assignee: Dave Barnes > Docs: geode-native user guide >> Security >> SSL setup needs update > --- > > Key: GEODE-2603 > URL: https://issues.apache.org/jira/browse/GEODE-2603 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes > > Update SSL setup to refer to OpenSSL's own installation procedures. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (GEODE-2592) Document Lucene-related gfsh commands
[ https://issues.apache.org/jira/browse/GEODE-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-2592: -- Assignee: Dave Barnes > Document Lucene-related gfsh commands > - > > Key: GEODE-2592 > URL: https://issues.apache.org/jira/browse/GEODE-2592 > Project: Geode > Issue Type: New Feature > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes > > Add four new Lucene-related gfsh commands to the gfsh command reference pages: > create lucene index, describe lucene index, list lucene indexes, search > lucene. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (GEODE-2592) Document Lucene-related gfsh commands
Dave Barnes created GEODE-2592: -- Summary: Document Lucene-related gfsh commands Key: GEODE-2592 URL: https://issues.apache.org/jira/browse/GEODE-2592 Project: Geode Issue Type: New Feature Components: docs Reporter: Dave Barnes Add four new Lucene-related gfsh commands to the gfsh command reference pages: create lucene index, describe lucene index, list lucene indexes, search lucene. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (GEODE-11) Lucene Integration
[ https://issues.apache.org/jira/browse/GEODE-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes updated GEODE-11: - Priority: Major (was: Minor) > Lucene Integration > -- > > Key: GEODE-11 > URL: https://issues.apache.org/jira/browse/GEODE-11 > Project: Geode > Issue Type: New Feature > Components: docs, querying >Reporter: Dan Smith >Assignee: xiaojian zhou > Labels: experimental > > This is a feature that has been under development for GemFire but was not > part of the initial drop of code for geode. > Allow Lucene indexes to be stored in Geode regions allowing users to do text > searches on data stored in Geode. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (GEODE-2591) User guide: Lucene headings should be reflected in navigation pane
[ https://issues.apache.org/jira/browse/GEODE-2591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-2591: -- Assignee: Dave Barnes > User guide: Lucene headings should be reflected in navigation pane > -- > > Key: GEODE-2591 > URL: https://issues.apache.org/jira/browse/GEODE-2591 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes > > The left-hand subnav for the Lucene section of the user guide does not match > the topics in the text. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (GEODE-2591) User guide: Lucene headings should be reflected in navigation pane
[ https://issues.apache.org/jira/browse/GEODE-2591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes updated GEODE-2591: --- Priority: Minor (was: Major) > User guide: Lucene headings should be reflected in navigation pane > -- > > Key: GEODE-2591 > URL: https://issues.apache.org/jira/browse/GEODE-2591 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Minor > > The left-hand subnav for the Lucene section of the user guide does not match > the topics in the text. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (GEODE-11) Lucene Integration
[ https://issues.apache.org/jira/browse/GEODE-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-11: Assignee: xiaojian zhou (was: Dave Barnes) > Lucene Integration > -- > > Key: GEODE-11 > URL: https://issues.apache.org/jira/browse/GEODE-11 > Project: Geode > Issue Type: New Feature > Components: docs, querying >Reporter: Dan Smith >Assignee: xiaojian zhou >Priority: Minor > Labels: experimental > > This is a feature that has been under development for GemFire but was not > part of the initial drop of code for geode. > Allow Lucene indexes to be stored in Geode regions allowing users to do text > searches on data stored in Geode. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (GEODE-11) Lucene Integration
[ https://issues.apache.org/jira/browse/GEODE-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-11: Assignee: Dave Barnes (was: xiaojian zhou) > Lucene Integration > -- > > Key: GEODE-11 > URL: https://issues.apache.org/jira/browse/GEODE-11 > Project: Geode > Issue Type: New Feature > Components: docs, querying >Reporter: Dan Smith >Assignee: Dave Barnes > Labels: experimental > > This is a feature that has been under development for GemFire but was not > part of the initial drop of code for geode. > Allow Lucene indexes to be stored in Geode regions allowing users to do text > searches on data stored in Geode. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (GEODE-2591) User guide: Lucene headings should be reflected in navigation pane
Dave Barnes created GEODE-2591: -- Summary: User guide: Lucene headings should be reflected in navigation pane Key: GEODE-2591 URL: https://issues.apache.org/jira/browse/GEODE-2591 Project: Geode Issue Type: Improvement Components: docs Reporter: Dave Barnes The left-hand subnav for the Lucene section of the user guide does not match the topics in the text. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (GEODE-11) Lucene Integration
[ https://issues.apache.org/jira/browse/GEODE-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes updated GEODE-11: - Priority: Minor (was: Major) > Lucene Integration > -- > > Key: GEODE-11 > URL: https://issues.apache.org/jira/browse/GEODE-11 > Project: Geode > Issue Type: New Feature > Components: docs, querying >Reporter: Dan Smith >Assignee: Dave Barnes >Priority: Minor > Labels: experimental > > This is a feature that has been under development for GemFire but was not > part of the initial drop of code for geode. > Allow Lucene indexes to be stored in Geode regions allowing users to do text > searches on data stored in Geode. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (GEODE-2561) Docs: error in gfsecurity.properties example (Geode User Guide)
[ https://issues.apache.org/jira/browse/GEODE-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-2561. Resolution: Fixed Fix Version/s: 1.2.0 Example corrected. Properties check out with current list. > Docs: error in gfsecurity.properties example (Geode User Guide) > --- > > Key: GEODE-2561 > URL: https://issues.apache.org/jira/browse/GEODE-2561 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes > Fix For: 1.2.0 > > > Reported by Mike Martell: > Looks like an error on this SSL Sample Impl page: > .../managing/security/ssl_example.html > Seems like they're using a path for a password: > ssl-truststore-password=/path/to/trusted.truststore > [db note] > Check entire page to make sure properties shown are consistent with the > current implementation, as security properties (in particular) were recently > revised. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (GEODE-2561) Docs: error in gfsecurity.properties example (Geode User Guide)
[ https://issues.apache.org/jira/browse/GEODE-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-2561: -- Assignee: Dave Barnes > Docs: error in gfsecurity.properties example (Geode User Guide) > --- > > Key: GEODE-2561 > URL: https://issues.apache.org/jira/browse/GEODE-2561 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes > > Reported by Mike Martell: > Looks like an error on this SSL Sample Impl page: > .../managing/security/ssl_example.html > Seems like they're using a path for a password: > ssl-truststore-password=/path/to/trusted.truststore > [db note] > Check entire page to make sure properties shown are consistent with the > current implementation, as security properties (in particular) were recently > revised. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (GEODE-2561) Docs: error in gfsecurity.properties example (Geode User Guide)
[ https://issues.apache.org/jira/browse/GEODE-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes updated GEODE-2561: --- Summary: Docs: error in gfsecurity.properties example (Geode User Guide) (was: Native client docs: error in gfsecurity.properties example) > Docs: error in gfsecurity.properties example (Geode User Guide) > --- > > Key: GEODE-2561 > URL: https://issues.apache.org/jira/browse/GEODE-2561 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Dave Barnes > > Reported by Mike Martell: > Looks like an error on this SSL Sample Impl page: > .../managing/security/ssl_example.html > Seems like they're using a path for a password: > ssl-truststore-password=/path/to/trusted.truststore > [db note] > Check entire page to make sure properties shown are consistent with the > current implementation, as security properties (in particular) were recently > revised. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (GEODE-2561) Native client docs: error in gfsecurity.properties example
Dave Barnes created GEODE-2561: -- Summary: Native client docs: error in gfsecurity.properties example Key: GEODE-2561 URL: https://issues.apache.org/jira/browse/GEODE-2561 Project: Geode Issue Type: Bug Components: docs Reporter: Dave Barnes Reported by Mike Martell: Looks like an error on this SSL Sample Impl page: .../managing/security/ssl_example.html Seems like they're using a path for a password: ssl-truststore-password=/path/to/trusted.truststore [db note] Check entire page to make sure properties shown are consistent with the current implementation, as security properties (in particular) were recently revised. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (GEODE-2486) Developer can use encrypted ciphers
[ https://issues.apache.org/jira/browse/GEODE-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes updated GEODE-2486: --- Component/s: docs > Developer can use encrypted ciphers > --- > > Key: GEODE-2486 > URL: https://issues.apache.org/jira/browse/GEODE-2486 > Project: Geode > Issue Type: New Feature > Components: docs, native client >Reporter: Jacob S. Barrett > > SSLImpl does not correctly initialize the OpenSSL library so ciphers other > than the NULL cipher can be used. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (GEODE-2527) geode-native docs: Fix broken links to Geode User Manual
[ https://issues.apache.org/jira/browse/GEODE-2527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-2527: -- Assignee: Dave Barnes > geode-native docs: Fix broken links to Geode User Manual > > > Key: GEODE-2527 > URL: https://issues.apache.org/jira/browse/GEODE-2527 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes > > The Geode Native User Guide contains links to the Geode User Manual > (designated "geodeman") that don't connect. > To find which files contain these references, you can grep the sources or you > can comment out the "geodeman" line in redirect.rb and try building the book. > I see 24 of these broken links. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (GEODE-2527) geode-native docs: Fix broken links to Geode User Manual
Dave Barnes created GEODE-2527: -- Summary: geode-native docs: Fix broken links to Geode User Manual Key: GEODE-2527 URL: https://issues.apache.org/jira/browse/GEODE-2527 Project: Geode Issue Type: Bug Components: docs Reporter: Dave Barnes The Geode Native User Guide contains links to the Geode User Manual (designated "geodeman") that don't connect. To find which files contain these references, you can grep the sources or you can comment out the "geodeman" line in redirect.rb and try building the book. I see 24 of these broken links. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (GEODE-2519) geode-native docs: add ASF copyrights
[ https://issues.apache.org/jira/browse/GEODE-2519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-2519. Resolution: Fixed This affected every geode-native doc file, so I committed directly without a pull request in order to minimize window in which conflicts might arise from the work of others. > geode-native docs: add ASF copyrights > - > > Key: GEODE-2519 > URL: https://issues.apache.org/jira/browse/GEODE-2519 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes > > The recently contributed docs need ASF copyright headers. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2519) geode-native docs: add ASF copyrights
[ https://issues.apache.org/jira/browse/GEODE-2519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15879330#comment-15879330 ] Dave Barnes commented on GEODE-2519: Using a Perl script provided by Karen Miller to take care of *.erb files (nearly all the sources). Hand editing files in the book directory. > geode-native docs: add ASF copyrights > - > > Key: GEODE-2519 > URL: https://issues.apache.org/jira/browse/GEODE-2519 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes > > The recently contributed docs need ASF copyright headers. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (GEODE-2512) Geode Native docs: book fails to build
[ https://issues.apache.org/jira/browse/GEODE-2512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-2512. Resolution: Fixed > Geode Native docs: book fails to build > -- > > Key: GEODE-2512 > URL: https://issues.apache.org/jira/browse/GEODE-2512 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes > > The geode native book fails to build. Need to update and correct the config > files in ../geode-native/docs/geode-native-book, and (once book generation is > restored) the README.md file needs to be updated. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (GEODE-2521) geode native docs: Document installation from source
[ https://issues.apache.org/jira/browse/GEODE-2521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes updated GEODE-2521: --- Description: Update installation instructions to include building from source. Binary distributions will also (presumably) be available on the website's Releases page. (See the installation section of the Geode user manual for a model to follow.) (was: Update installation instructions to include building from source. Binary distributions will also (presumably) be available on the website's Releases page.) > geode native docs: Document installation from source > > > Key: GEODE-2521 > URL: https://issues.apache.org/jira/browse/GEODE-2521 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dave Barnes > > Update installation instructions to include building from source. Binary > distributions will also (presumably) be available on the website's Releases > page. (See the installation section of the Geode user manual for a model to > follow.) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (GEODE-2519) geode-native docs: add ASF copyrights
[ https://issues.apache.org/jira/browse/GEODE-2519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-2519: -- Assignee: Dave Barnes > geode-native docs: add ASF copyrights > - > > Key: GEODE-2519 > URL: https://issues.apache.org/jira/browse/GEODE-2519 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes > > The recently contributed docs need ASF copyright headers. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (GEODE-2512) Geode Native docs: book fails to build
[ https://issues.apache.org/jira/browse/GEODE-2512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-2512: -- Assignee: Dave Barnes > Geode Native docs: book fails to build > -- > > Key: GEODE-2512 > URL: https://issues.apache.org/jira/browse/GEODE-2512 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes > > The geode native book fails to build. Need to update and correct the config > files in ../geode-native/docs/geode-native-book, and (once book generation is > restored) the README.md file needs to be updated. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (GEODE-2513) Geode Native docs: rebrand to match open-source software
[ https://issues.apache.org/jira/browse/GEODE-2513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes updated GEODE-2513: --- Issue Type: Improvement (was: Bug) > Geode Native docs: rebrand to match open-source software > > > Key: GEODE-2513 > URL: https://issues.apache.org/jira/browse/GEODE-2513 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dave Barnes > > The newly-contributed Geode Native doc sources contain some GemFire artifacts > that have been purged from the open-source code. Docs should be updated to > match. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
