API).
REST API
I've found that most don't want to use the Dev REST API because it's
attached to a server rather than the cluster. HA?
*Wes Williams | Pivotal Advisory **Data Engineer*
781.606.0325
http://pivotal.io/big-data/pivotal-gemfire
On Tue, Apr 25, 2017 at 7:01 PM, Fre
tps://github.com/apache/geode/tree/rel/v1.1.1/geode-core/src/main/java/org/apache/geode/management/internal/cli/commands
Or somewhere else?
*Wes Williams | Pivotal Advisory **Data Engineer*
781.606.0325
http://pivotal.io/big-data/pivotal-gemfire
On Tue, Apr 25, 2017 at 11:41 PM, Jacob Barrett wrote:
+1 to utility functions
*Wes Williams | Pivotal Advisory **Data Engineer*
781.606.0325
http://pivotal.io/big-data/pivotal-gemfire
On Wed, May 24, 2017 at 4:59 PM, John Blum wrote:
> On a side but related note, it would be nice if Geode had the notion of
> useful, "canned" Fu
I'm not clear on the reference to "I like the idea of first class data
structures like Lists and Sorted Sets."
Is the suggestion here to extend Geode to not only support a distributed
ConcurrentHashMap but also distributed ConcurrentList's and
ConcurrentSortedSet's?
>>Replicating a whole collection because of 1 change does not really make
too much sense.<<
I agree but won't delta replication prevent sending the entire collection
across the wire?
*Wes Williams | Pivotal Advisory **Data Engineer*
781.606.0325
http://pivotal.io/big-data/pivota
And correcting the spelling of "SEPERATOR" would be a plus while changing
the code.
*Wes Williams | Pivotal Advisory **Data Engineer*
781.606.0325
http://pivotal.io/big-data/pivotal-gemfire
On Mon, Mar 6, 2017 at 6:14 PM, galen-pivotal wrote:
> Github user galen-pivotal commented
Most new customers just want Geode/ GemFire to work - easily - because most
projects don't require dealing with PDX. In fact, some explicitly tell me
that they don't want to know about PDX because it's a distraction for the
simple use-cases. This is, of course, with the caveat that unless they need
ould intentionally inject malicious code into the grid? Whereas
gfsh> deploy --jar=... gives Operations a control check point that
theoretically can thwart such an attack.
*Wes Williams | Pivotal Advisory **Data Engineer*
781.606.0325
http://pivotal.io/big-data/pivotal-gemfire
On Fri, Jan 6, 2
Wes Williams created GEODE-2570:
---
Summary: Export cluster-configuration returns "GemFire error"
message
Key: GEODE-2570
URL: https://issues.apache.org/jira/browse/GEODE-2570
Proj
[
https://issues.apache.org/jira/browse/GEODE-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15900055#comment-15900055
]
Wes Williams commented on GEODE-2570:
-
This is a "broken window" that g
[
https://issues.apache.org/jira/browse/GEODE-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wes Williams updated GEODE-2722:
“So the default pattern would match all class names?”
This is the most usual case and I believe
[
https://issues.apache.org/jira/browse/GEODE-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15945582#comment-15945582
]
Wes Williams commented on GEODE-2725:
-
The --dir option works but you need to
Wes Williams created GEODE-2270:
---
Summary: Need API to call gfsh and get results dynamically from
code
Key: GEODE-2270
URL: https://issues.apache.org/jira/browse/GEODE-2270
Project: Geode
[
https://issues.apache.org/jira/browse/GEODE-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15801659#comment-15801659
]
Wes Williams commented on GEODE-2270:
-
There was a thread on this topic in the g
[
https://issues.apache.org/jira/browse/GEODE-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wes Williams updated GEODE-2270:
Description:
GIVEN:
1) The GfshParser and CommandResult are internal classes.
2) CommandResult
[
https://issues.apache.org/jira/browse/GEODE-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wes Williams updated GEODE-2270:
Description:
GIVEN:
1) The GfshParser and CommandResult are internal classes.
2) CommandResult
[
https://issues.apache.org/jira/browse/GEODE-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15804708#comment-15804708
]
Wes Williams commented on GEODE-2268:
-
I think it simpler to keep the jars on
17 matches
Mail list logo
