A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::open($save_path, $name) should either be compatible with SessionHandlerInterface::open(string $path, string $name): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 6

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::close() should either be compatible with SessionHandlerInterface::close(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 7

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::read($session_id) should either be compatible with SessionHandlerInterface::read(string $id): string|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 8

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::write($session_id, $session_data) should either be compatible with SessionHandlerInterface::write(string $id, string $data): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 9

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::destroy($session_id) should either be compatible with SessionHandlerInterface::destroy(string $id): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 10

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::gc($maxlifetime) should either be compatible with SessionHandlerInterface::gc(int $max_lifetime): int|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 11

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 284

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_set_cookie_params(): Session cookie parameters cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 291

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 306

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 316

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 317

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 318

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 319

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 377

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_set_save_handler(): Session save handler cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 110

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_start(): Session cannot be started after headers have already been sent

Filename: Session/Session.php

Line Number: 143

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

NRIPage | Articles | Yashasvi Jaiswal Leaves Mumbai for Goa Amid Rift With Ajinkya Rahane, Set for Leadership Role | Get Latest International News & Updates. Your Source for World Events and Updates - NRI Page
Edit

Yashasvi Jaiswal Leaves Mumbai for Goa Amid Rift With Ajinkya Rahane, Set for Leadership Role

Yashasvi Jaiswal Leaves Mumbai for Goa Amid Rift With Ajinkya Rahane, Set for Leadership Role

In a surprising move that has stunned Indian domestic cricket circles, India opener Yashasvi Jaiswal has decided to part ways with Mumbai and join Goa for the upcoming 2025-26 season. The Mumbai Cricket Association (MCA) confirmed on Wednesday that they had accepted Jaiswal’s request to transfer, marking the end of a significant chapter in the 23-year-old's career. Jaiswal, who has risen through the ranks of Mumbai cricket to become a national team regular, revealed in an interview that the decision to move was not easy but was made in pursuit of new opportunities—possibly including a captaincy role with the Goa team.
 

"It was a very tough decision for me. Whatever I am today is because of Mumbai. The city has made me who I am, and all my life, I will be indebted to the MCA," Jaiswal told The Indian Express. "Goa has thrown me a new opportunity and it has offered me a leadership role." He further added that while his primary focus remains on performing for India, he will contribute to Goa's domestic season whenever he's not on national duty.

 

Reports Point to Tension With Mumbai Team Management

While Jaiswal's official reason for leaving was framed around leadership and new challenges, multiple media reports suggest deeper underlying issues in the Mumbai camp led to his exit. A report by India Today claims that the young batter was unhappy with constant scrutiny and criticism from the Mumbai team management, particularly from Ajinkya Rahane, the captain of Mumbai's First-Class team. Tensions between the two reportedly date back to 2022, when Rahane sent Jaiswal off the field during a Duleep Trophy game for excessive sledging of South Zone batter Ravi Teja—even though Jaiswal had scored a mammoth 265 earlier in the same match.
 

Sources cited in the report described the relationship between Rahane and Jaiswal as “untenable”, suggesting that the two never fully resolved their differences. The situation allegedly worsened during the Mumbai vs Jammu & Kashmir game last season, where Jaiswal was criticized for a rash shot in a crucial situation. Mumbai coach Omkar Salvi and Rahane both reportedly questioned his commitment, leading to a heated exchange. In an emotional reaction, Jaiswal is said to have kicked Rahane's kitbag in the dressing room.

 

PTI Confirms Dispute With Senior Player

The Press Trust of India (PTI) also reported on the situation, indicating that Jaiswal had a rift with a senior player during the J&K match. The issue once again centered around shot selection, with a senior cricketer questioning Jaiswal’s approach during a difficult phase of the game. The young left-hander reportedly retaliated by pointing out the senior’s own mistakes in the first innings. “It is also believed Jaiswal's decision to move to Goa could be due to his displeasure with the Mumbai team management,” the PTI report noted. While no official statement has been made by Rahane or the MCA regarding the reports of a fallout, the widespread consistency in multiple sources suggests that internal discord played a significant role in Jaiswal's exit.

 

A New Chapter With Goa

Goa, who have been working to revamp their domestic cricket structure, will be hoping that Jaiswal brings both performance and leadership to their squad. The left-hander is expected to take on captaincy responsibilities, although his availability will depend on India's international calendar. Jaiswal's departure marks a significant shift for Mumbai cricket, which has long been a powerhouse in Indian domestic cricket. It also raises questions about player management, internal politics, and the handling of young talent in state teams. Whether Jaiswal thrives in Goa and takes on a leadership mantle successfully, or whether the move marks just a temporary chapter, only time will tell. But for now, Indian cricket fans are watching closely as one of the country's most promising young talents steps into unfamiliar territory.

What is your response?

joyful Joyful 0%
cool Cool 0%
thrilled Thrilled 0%
upset Upset 0%
unhappy Unhappy 0%
AD
AD