Hello everyone,
I neglected to put an end date on this RFC, but it's been open for 2+ weeks
now, and I believe we're close to (at?) consensus, so I would like to close
it out and move on ASAP. If you still have anything urgent to add, please
reply here and let's hash it out. All other things bei
Thanks. My goal is actually to help increase the size and reach of the Geode
community with a place to post blogs, videos, and other collateral featuring
best practices, tutorials, use cases, and the like. The current Geode site
infrastructure doesn't seem well-suited to that. I'm thinking of
Hello Geode devs and users,
I have a set of files populated with data, fairly distributed, I want to
put each file's data in a specific bucket,
like PutAll File-0 data into Geode bucket B0
PutAll File-1 data into Geode bucket B1
and so on...
How can i achieve this using geode client.
Hello Geode devs and users,
I have a set of files populated with data, fairly distributed, I want to
put each file's data in a specific bucket,
like PutAll File-0 data into Geode bucket B0
PutAll File-1 data into Geode bucket B1
and so on...
How can i achieve this using geode client.
Hello Geode devs and users,
I have a set of files populated with data, fairly distributed, I want to
put each file's data in a specific bucket,
like PutAll File-0 data into Geode bucket B0
PutAll File-1 data into Geode bucket B1
and so on...
How can i achieve this using geode client.
Bob,
Your ideas are welcome! I do like the idea of an aggregation point for Geode
content. Our past experience with the Apache JRoller blog site was…not the
best. We do have some content aggregated in the wiki [1] but it’s not a great
content platform either.
My main concerns are a) ensurin
Recently it’s been noticed that spring-core-5.2.1.RELEASE.jar is getting
flagged for “high" security vulnerability CVE-2020-5398.
Analysis shows that Geode does not use Spring in a manner that would expose
this vulnerability (none of our REST apis or pulse set a Content-Disposition
header deriv
+1
On Fri, Apr 10, 2020 at 11:16 AM Owen Nichols wrote:
> Recently it’s been noticed that spring-core-5.2.1.RELEASE.jar is getting
> flagged for “high" security vulnerability CVE-2020-5398.
>
> Analysis shows that Geode does not use Spring in a manner that would
> expose this vulnerability (none
+1
Based on: The risk is low. Avoids false positives in automated
vulnerability scans.
On Fri, Apr 10, 2020 at 12:33 PM Dick Cavender wrote:
> +1
>
> On Fri, Apr 10, 2020 at 11:16 AM Owen Nichols wrote:
>
> > Recently it’s been noticed that spring-core-5.2.1.RELEASE.jar is getting
> > flagged f
Yes, you can use partition resolver to achieve this.
You can also look into "StringPrefixPartitionResolver" which doesn't need
custom implementation.
https://geode.apache.org/docs/guide/111/developing/partitioned_regions/standard_custom_partitioning.html
-Anil
On Fri, Apr 10, 2020 at 11:08 AM st
Hi Steve,
The bucket that data goes into is generally determined by the key. So for
example if your data in File-0 is all for customer X, you can include
Customer X in your region key and implement a PartitionResolver that
extracts the customer from your region key and returns it. Geode will then
+1
-Dan
On Fri, Apr 10, 2020 at 12:37 PM Anilkumar Gingade
wrote:
> +1
> Based on: The risk is low. Avoids false positives in automated
> vulnerability scans.
>
> On Fri, Apr 10, 2020 at 12:33 PM Dick Cavender
> wrote:
>
> > +1
> >
> > On Fri, Apr 10, 2020 at 11:16 AM Owen Nichols
> wrote:
>
There appears to be consensus to bring this critical fix to support/1.12. I
have done git cherry-pick -x ead319cc04e284838275669c2d502e1a8c5ad822 and
updated GEODE-7970 to add 1.12.1 to the list of fixed versions.
Thanks
-Owen
> On Apr 10, 2020, at 1:24 PM, Dan Smith wrote:
>
> +1
>
> -Dan
Thanks Dan for your quick response.
Though, This may not be a recommended pattern, Here, I am targeting a
bucket specific putAll and want to exclude hashing as it turn out as an
overhead in my scenario.
Is this achievable...? How should I define a PartionResolver that works
generically and returns
Hi Steve,
Well, you can technically use more than just the key in your partition
resolver. You can also use a callback argument, something like the below
code. This would put all of your data into bucket 0. The issue is that all
operations will have to pass the callback argument, so if you need t
Did you look into:"StringPrefixPartitionResolver" which doesn't need custom
implementation.
https://geode.apache.org/docs/guide/111/developing/partitioned_regions/standard_custom_partitioning.html
You can try key like - "key | file1"
-Anil.
On Fri, Apr 10, 2020 at 4:02 PM Dan Smith wrote:
> H
16 matches
Mail list logo
