Trace flag 10260 on SQL Server 2016

Question

Our SQL Server 2016 development servers have trace flag 10260 set on start up. The other servers that run SQL Server 2016 do not.
I've searched high and low, but have not been able to find any info on the subject.

What does this trace flag do?

Is it safe to remove?

Answer 1

At some point in the pre-RTM phase, it was used for some Polybase related process. As far as I can tell, it's 10260 is no longer in use for RTM so you can remove. Doesn't actually do anything anymore.