Consider to not use a calendar date picker.
Take a step back and try to figure out how people are going to use this filter. How far back are they likely to choose the "from" date? If this can be years, a date picker can make that very inconvenient. Is it a possibility that users just want to select a year and not be bothered with selecting a month and a day too? In that case consider using select boxes for years, months and days and provide the option "any" for each. You can make "any" the default, but I would recommend to collect data from it and adjust the default value after a while when it is clear what values are used most. If the years select box gets very long, it can also be a number input.
For the "to" date this is slightly different. Still you want to use select boxes to keep it consistent, but there is no "any" option as that makes no sense here. The default can be the current date, if that is mostly wanted. But you can also add a checkbox to choose a different date than today and keep the select boxes disabled until the checkbox is checked. That way you can provide an easy way to only select (or enter) a year and leave month and day the default. The default values can be: current year or last year, January 1st or December 31st, it depends on the needs.
To take it a step further, you can also offer some presets. If a pattern shows that users just want to select past year or month to filter, why not give them that option directly? You can add options like "Past three months", "Last year", "This week" etc. Add a select box (or radio buttons) with presets for the most commonly used periods and offer an extra option to choose a different date. When choosing a different date it will show/enable the select boxes as explained above.
Is there a standard for this?
No, it all depends on the context and user. I think the overall message is that you should know why this filter exists and what date ranges users are going to filter.