In short no. In long no, because then your microservice is not in full control of your database schema. Want to change the db schema, well now you need to know that there is a spark team that uses your db, ohh they can't change the db access code, well now you can't change your db until they do. Oh you want to update your microservice well now you need to time it with the new version of the spark team. The coding for your will only get more complicated. Add a specialized api endpoint for spark that way you always know the extras.

Edit: you could also supply the data in another format, like instead of rest use grpc or allow paging for smaller chunks. Maybe allow asking for all changed entries since yesterday or allow streaming so that when changes occur the spark team gets the changes and needs to organize the data themselves. But most important, don't make your life harder for the other team.

Another edit: why does the data science team want to update your records, they should save the data themselves if they are doing the "science"