Cricket Country Staff
Editorial team of CricketCountry.
Written by Cricket Country Staff
Published: Dec 14, 2018, 03:56 PM (IST)
Edited: Dec 14, 2018, 03:56 PM (IST)
Michael Clarke, the former Australia captain, believes that on the evidence of the opening day’s play in Perth, Virat Kohli’s Indian team have erred in not playing a specialist spinner for the second Test.
On an up-and-down pitch at Optus Stadium – hosting its first Test match – India’s four-pronged pace attack managed four wickets with the big scalps of Marcus Harris (70) and Shaun Marsh (45) going to Hanuma Vihari. In his second Test, Vihari bowled 14 overs of offspin on Friday and dismissed Harris with a ball that got big on the batsman could only fend it to slip.
ALSO READ: The third time India have gone for an all-pace attack
After tea, Marsh was hurried into a cut shot and edged to slip. Seeing Vihari take two wickets on day one, Clarke was moved to wonder why India did not pick Ravindra Jadeja in place of the injured R Ashwin.
“Watching him [Vihari] take wickets, I have no doubt that India missed a trick by not playing a spinner,” said Clarke on a post-play show. “I think Ravindra Jadeja would have taken wickets, and seeing the wicket I think Nathan Lyon is going to have a big role.”
ALSO READ: India keep Australia to 277/6 on up-and-down Perth surface
Clarke’s former team-mate Michael Hussey concurred. “Having someone like Ashwin would have been nice … I know they had Jadeja for this Test [as an option] … to keep it tight and rotate the fast bowlers. I think Lyon will have a big role to play,” he said on air after stumps.
Lyon claimed seven wickets at Optus Stadium during a Sheffield Shield match earlier this month, including four in the second innings, and after the win for New South Wales he spoke of how excited he was to return to play India.
This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.
Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.
If you disable this cookie, we will not be able to save your preferences. This means that every time you visit this website you will need to enable or disable cookies again.