GitHub user svscorp opened a pull request:
https://github.com/apache/cloudstack/pull/185
GetUsageRecordsCmd - NewInputFormat for START_DATE and END_DATE
It is extremely useful to be able to narrow the output to the specific time
range within a date.
You can merge this pull request
Github user svscorp commented on the pull request:
https://github.com/apache/cloudstack/pull/185#issuecomment-95592190
After making more tests, there is one more commit added to remove
unnecessary adjustToDayStart/End code, since ParamProcessWorker is actually
taking care of building
Github user svscorp commented on the pull request:
https://github.com/apache/cloudstack/pull/185#issuecomment-95872015
@bhaisaab Oh yes, it would be perfect. Should I make a PR, Rohit?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
GitHub user svscorp opened a pull request:
https://github.com/apache/cloudstack/pull/191
Get usage records new input format start date end date (for 4.5 branch)
Port of an improvement from PR: #185
@bhaisaab @kishankavala Here it is.
You can merge this pull request into a
Github user svscorp commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/191#discussion_r29093521
--- Diff: server/src/com/cloud/usage/UsageServiceImpl.java ---
@@ -224,11 +224,11 @@ public boolean
generateUsageRecords(GenerateUsageRecordsCmd cmd
Github user svscorp closed the pull request at:
https://github.com/apache/cloudstack/pull/191
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Github user svscorp commented on the pull request:
https://github.com/apache/cloudstack/pull/191#issuecomment-96160523
Thanks
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
