[CONJ-995] Duplicate rows are returned in streaming ResultSet. Created: 2022-07-26  Updated: 2023-11-06

Status: Needs Feedback
Project: MariaDB Connector/J
Component/s: aurora, mysql_compatibility
Affects Version/s: 2.4.4
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Pranjal Gupta Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: DuplicateRows
Environment:

UBUNTU, Java application.


 Description   

We are using AWS Aurora Mysql as out database and mariadb-java-client (version: 2.4.4). When we stream the ResultSet from database then some times size of the ResultSet increases continuously and it is more then the provided FetchSize parameter. And duplicate rows are retrieved from the database.

  • This issue occurs randomly some times only not always.
  • Query does not produce any data which can contain duplicate rows
  • When exactly same query is run directly on the database (via some database workbench) there are no duplicate rows.
  • According to documentation resultSet id fully fetched when some other query is executed on the same connection but this is not happening in our case. Even if this is happening the remaining data should be fetched as per documentation so there should be no duplicates. Can you please help check this if there is some bug or some other reason which could cause this kind of issue. From our side we have investigated our code base quite thoroughly and did find any bug, due to company policy I can not share code base but feel free to ask any questions if you need.

 Comments   
Comment by Ralf Gebhardt [ 2022-07-28 ]

Hi Pranjal, MariaDB Connector/J 2.4 is not in maintenance anymore for several years already. Do you see the same happening with version 2.7?

Comment by Pranjal Gupta [ 2022-08-01 ]

Thank you for the response ralf.gebhardt@mariadb.com.
Sorry I have not tried it with any other version, since this library is used by almost all of our services and upgrading the version and testing it would be very long task so we will consider upgrading it in near future. I understand it is not maintained anymore, but if possible can you please provide some possible reasons why this could be happening.
Thanks!

Generated at Thu Feb 08 03:19:50 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.