Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GEODE-2098: Moved gfsh history file location from .gemfire to .geode #283

Closed
wants to merge 1 commit into from
Closed

GEODE-2098: Moved gfsh history file location from .gemfire to .geode #283

wants to merge 1 commit into from

Conversation

davinash
Copy link
Contributor

Made the code changes and added a test for the same.

Following Test is failing with precheckin, but works fine when ran individually.
org.apache.geode.internal.statistics.DiskSpaceLimitIntegrationTest

Made the code changes and added a test for the same.
@kirklund
Copy link
Contributor

Since Geode 1.0 released using .gemfire history file, we should probably read and use .gemfire if .geode does not exist. If both files exist then .geode should take precedence.

What OS does DiskSpaceLimitIntegrationTest fail on for you?

@kirklund
Copy link
Contributor

I recommend discussing backwards compatibility of .gemfire vs .geode directory (which contains gfsh history file) on the dev list. I don't really feel strongly one way or the other (supporting .gemfire vs just a hard switch to .geode). Dev list is good place to discuss backwards compatibility though.

@upthewaterspout
Copy link
Contributor

IMO losing your gfsh history on an upgrade is probably not a big deal.

@metatype
Copy link
Contributor

Agreed. This could be handled in a release note: “If you want to preserve your gfsh history, please copy…”

Anthony

On Nov 14, 2016, at 10:57 AM, Dan Smith notifications@github.com wrote:

IMO losing your gfsh history on an upgrade is probably not a big deal.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub #283 (comment), or mute the thread https://github.com/notifications/unsubscribe-auth/ACqT2dEBRv5RJyZjnBFGW1o76-yAooPwks5q-K7_gaJpZM4KxirC.

@davinash
Copy link
Contributor Author

@kirklund
What OS does DiskSpaceLimitIntegrationTest fail on for you?
[ Avinash ] Linux

@davinash
Copy link
Contributor Author

Thanks @kirklund @metatype @upthewaterspout. Do I need to mark the JIRA for release notes ? If not I will merge this PR, please let me know.

@kirklund
Copy link
Contributor

+1 looks ready to push to develop.

Once it's committed on develop, then mark the Jira ticket Resolved (not Closed) and Fix Version(s) should say 1.1.0-incubating. When 1.1.0 is released, all Resolved tickets are moved to Closed (all such tickets will be part of release notes automatically I think).

@davinash
Copy link
Contributor Author

Thanks @kirklund, @metatype I have followed the process from https://cwiki.apache.org/confluence/display/GEODE/Code+contributions
Please do let me know if everything is correct.

@kirklund
Copy link
Contributor

I tried to pull this in but I get an error message about the branch not existing:

fatal: Couldn't find remote ref feature/GEODE-2098

Looks like the pull request is still open, but the branch has been destroyed.

@davinash
Copy link
Contributor Author

closing the pull request.

@davinash davinash closed this Nov 29, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants