Hi Jason,
I tried to upgrade from 6.6.2 to 7.1.0 and got the following exception:
org.apache.lucene.index.IndexFormatTooNewException: Format version is not
supported (resource BufferedChecksumIndexInput(segments_2)): 7 (needs to be
between 4 and 6)
It looks like the fix is not good.
What I se
Hi all,
I wrote up a proposal for Certificate Based Authorization.
Please review and comment on the below proposal.
https://cwiki.apache.org/confluence/display/GEODE/Certificate+Based+Authorization
BR,
Mario
Šalje: Udo Kohlmeyer
Poslano: 2. prosinca 2019. 20:10
We have completed the work to move the gfsh code into a separate gradle
submodule. This work has the following implications and effects:
- geode-core does not have any direct dependencies on Spring libraries
anymore
- Anyone building with Geode will need to include the '*geode-gfsh'*
d
Apologies to anyone who has any gfsh related PRs in flight as it will
require rebasing onto develop.
--Jens
On Fri, Dec 6, 2019 at 6:27 AM Jens Deppe wrote:
> We have completed the work to move the gfsh code into a separate gradle
> submodule. This work has the following implications and effect
👏 This 👏 is 👏 amazing 👏
> On Dec 6, 2019, at 6:27 AM, Jens Deppe wrote:
>
> We have completed the work to move the gfsh code into a separate gradle
> submodule. This work has the following implications and effects:
>
> - geode-core does not have any direct dependencies on Spring libraries
>
+1
On Thu, Dec 5, 2019 at 7:40 PM Dan Smith wrote:
> Hi,
>
> I wrote up a proposal for deprecating of the singleton PoolManager in favor
> of a ClientCache scoped service. Please review and comment on the below
> proposal.
>
> I think this should address the issues that Spring Data Geode and fri
This is a great idea!
On thought though, did you consider just converting the existing PoolManager to
an interface leaving the static methods intact but deprecated? I would think
this would make existing code pretty easy to refactor over to the new code with
minimal changes. If you thought abou
+1
On Thu, Dec 5, 2019 at 4:40 PM Dan Smith wrote:
> Hi,
>
> I wrote up a proposal for deprecating of the singleton PoolManager in favor
> of a ClientCache scoped service. Please review and comment on the below
> proposal.
>
> I think this should address the issues that Spring Data Geode and fri
> if one gw receiver stops, the locator will publish to any remote locator
that there are no receivers up.
I am not sure if locators proactively update remote locators about change
in receivers list rather I think the senders figures this out on connection
issues.
But I see the problem that local-
Did the class path in geode-dependencies.jar change? If so, that might also
affect applications that relied on the those (spring) jars being available on
the class path. Of course, they can fix that by explicitly injecting the
applications dependencies into the class path as needed.
Anthony
Thanks for the write-up. I think it does require a bit of clarification
around how the functionality is enabled.
You've stated:
For client connections, we could presume that certificate based
> authorization should be used if both features are enabled, but the client
> cache properties don’t prov
Jake wrote:
> On thought though, did you consider just converting the existing
> PoolManager to an interface leaving the static methods intact but
> deprecated?
>
Dale wrote:
> To the extent possible without breaking existing APIs, please name the new
> stuff to indicate what’s in the pool (E.g.
The geode-dependencies.jar now includes the *geode-gfsh.jar* (as well as
Spring still).
--Jens
On Fri, Dec 6, 2019 at 8:49 AM Anthony Baker wrote:
> Did the class path in geode-dependencies.jar change? If so, that might
> also affect applications that relied on the those (spring) jars being
>
Just to be clear, this effort does *not* result in a standalone gfsh
executable/jar.
Sorry.
--Jens
On Fri, Dec 6, 2019 at 6:27 AM Jens Deppe wrote:
> We have completed the work to move the gfsh code into a separate gradle
> submodule. This work has the following implications and effects:
>
>
Alberto,
Can you please file a JIRA ticket for this. This could come up often as
more and more deployments move to K8s.
-Anil.
On Fri, Dec 6, 2019 at 8:33 AM Sai Boorlagadda
wrote:
> > if one gw receiver stops, the locator will publish to any remote locator
> that there are no receivers up.
>
> On Dec 6, 2019, at 9:43 AM, Jens Deppe wrote:
>
> The geode-dependencies.jar now includes the *geode-gfsh.jar* (as well as
> Spring still).
Should it??
> On Dec 6, 2019, at 9:44 AM, Jens Deppe wrote:
>
> Just to be clear, this effort does *not* result in a standalone gfsh
> executable/jar.
Is this a future plan?
Our goal wasn’t to make gfsh standalone, but a couple people have asked about
it already. It’s not currently planned as far as I know, though maybe it will
be in the future.
> On Dec 6, 2019, at 10:00 AM, Jacob Barrett wrote:
>
>
>
>> On Dec 6, 2019, at 9:43 AM, Jens Deppe wrote:
>>
>> Th
> Dale - are you suggesting a ConnectionPoolService that returns ConnectionPool
> instances?
Yes.
> Would that mean ConnectionPool would extend Pool and we would deprecate Pool
> itself?
Maybe extend. I worry about extending, for two reasons.
First, extending would make the new interface dep
> On Dec 6, 2019, at 9:40 AM, Dan Smith wrote:
>
> Regarding changing PoolManager to
> an interface, I guess originally I wasn't thinking we would still be
> backwards compatible if we did that. But as I think about it I think that
> might be ok. One slight issue with that approach is that we h
Hi Mario,
I made a PR against your branch for some of the changes I had to do to get
past the Index too new exception. Summary - repo creation, even if no
writes occur, appear to create some meta data that the old node attempts to
read and blow up on.
The pr against your branch just prevents the
I imagine once the Management v2 API's are GA (and feature complete), I
don't see a reason why /gfsh/ should not be a stand alone module. It
would definitely have to be updated to use the new v2 API's, which
should not have any direct dependency on geode-core any more.
On 12/6/19 10:01 AM, Jac
Any standalone management API or client thereof would not be able to start
locator or start server. For that gfsh still needs a large chunk of Geode.
> On Dec 6, 2019, at 12:25 PM, Udo Kohlmeyer wrote:
>
> I imagine once the Management v2 API's are GA (and feature complete), I don't
> see
23 matches
Mail list logo
