Yeah, I think so too.
Yaning, how about having a JIRA for these issues targeting for RC2?
Sorry I'm in sick leave these days and I will check the package today.
Regards,
Kai
-Original Message-
From: Emmanuel Lécharny [mailto:elecha...@gmail.com]
Sent: Sunday, September 13, 2015 9:54
Hi,
I have looked at the code today, and I found that the way we handle the
BtreeHeader is a bit complex, and does not fit some other ideas I had
regarding the management of transactions.
Currently, we store a map of BH where for each BTree, we have the latest
BH (ie, the one associated with the
[
https://issues.apache.org/jira/browse/DIRKRB-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiajia Li updated DIRKRB-407:
-
Description:
Now the tool's usage in windows is "bin/start-kdc.cmd", it should be changed to
[
https://issues.apache.org/jira/browse/DIRKRB-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiajia Li updated DIRKRB-407:
-
Description:
Now the tool's usage in windows is "bin/start-kdc.cmd", it should be changed to
[
https://issues.apache.org/jira/browse/DIRKRB-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiajia Li updated DIRKRB-407:
-
Attachment: DIRKRB-407-V1.patch
Print the right usage in windows env.
> Fix tool's usage in windows
>
