so I have defined a periodic calendar with following periods,
Period A: to factor in start of every month
Period B: to factor in end of every month
Calendar
Now I am trying to schedule the job on every days marked as period A i.e. start of every month by doing the following settings,
Scheduling Setting
Schedule
My Problem
From July month the schedule is getting pre-shifted by 1. Any ideas why?
Also can someone guide me to a detailed documentation on periodic calendars and the values example?
Thanks.
I was not able to reproduce the specific issue you are having. I created the same periodic calendar (Per A = SoM, Per B = EoM) and my job schedule came out as expected.
Calendar
Job
Schedule
Solution
There is no need to use a periodic calendar for such a simple scheduling requirement. Making use of a periodic calendar incurs maintenance overhead as you need to ensure it is updated every year.
Instead of using a periodic calendar you could simply configure the job as below. This will result in a job that will always execute on the first day of each month, no maintenance required.
Related
Does somebody know the difference between the ODATE and the RDATE? The manual says:
ODATE --> Original scheduling date of the job.
RDATE --> Installation current working date.
But that is not helpful for me.
Thanks a lot.
The ODATE is when the job is scheduled for originally and you need to take into account 2 things; i) when is your New Day Processing (i.e. if it's 06:00 am each day then the ODATE runs from 6am-6am and will be the same for that whole period) ii) you don't necessarily have to order with the date set as the current date - e.g. today you might want to order in jobs where some are scheduled for the last day of the month due to batch processing considerations.
%%$RDATE or %%RDATE (one value gives the year as yyyy, the other as yy) will resolve to the current system date. Whatever your server is saying the local date is now, regardless of Control-M settings, the RDATE will give you that. Often this setting is used if your job could run on different days but you really need to have today's date in the processing.
Of course, if your New Day Processing runs at midnight, you always clear all jobs away during NDP and you never order jobs into the future - then RDATE and ODATE will be basically the same.
Is there any way to implement current plan concept in Airflow..
Example: In Control m jobs will be scheduled as per date example: ODATE : 20200801
But in airflow we are not able to see an option how to schedule the jobs as per every date/calendar..
Is there any best way we can implement..
I need to put a scheduler in an app that will make a weekly schedule without dates. For example weekly dinner schedule. Or chores schedule, etc. Really just need day of week and time mapped.
Fullcalendar's Scheduler is the perfect format, except it deals with specific dates.
Is there a way I can use it for my use case? Scheduling weekly events without them being tied to specific dates?
I would like to obtain data via the Google analytics api (Java). Every half an hour once I would be running a script which needs to get me the required variables over the previous half an hour, that is details of the person who has used my site over the last half hour. I do not know if this is possible since the start date and end date parameters can be used only in date format and not in datetime format. How should I proceed with this? Thanks in advance
Google Analytics core reporting API provides 2 dimensions which are the hour and the minute. This should allow you to accomplish what you want, just make sure to wait till the hour and minute you are querying are updated.
Check
https://developers.google.com/analytics/devguides/reporting/core/dimsmets#view=detail&group=time&jump=ga_hour
I'm trying to implement the graph from this blog post: http://blog.neo4j.org/2012/02/modeling-multilevel-index-in-neoj4.html
Inside the blogpost is a schematic of the graph and a query on how to find a range of events. However in my use case i don't have a set consecutive days. So for example the current state of the graph could be that i have day nodes from 12-7-2013 (12 july 2013) to 12-8-2013 (12 august 2013). Then when adding an event on 12-7-2014 i'm missing all the inbetween days for a whole year!
First problem is if i start to write queries that generate those days it might become very slow (application needs to be responsive). Second problem is i end up with days on which no event could be taken place, and so have unneeded data in my database.
So my question is: How can i get a range of events without using the NEXT relation between days?