I experienced this issue recently while syncing a database from an Acquia hosted dev environment to my local environment. This error led me to investigate the dump file which I found included global transaction identifier (GTID) sets. I was able to work around this issue by suppressing the GTID sets using the --set-gtid-purged=OFF option for the mysqldump command. Combining that option with the drush sql-sync command allows a successful sync.
A local Drupal environment can be created in many different ways. I recommend this approach for many reasons. Most of all, this method is used by many of the top professionals to develop enterprise Drupal sites. Additionally, it's automated, and easy enough for a beginner to get started, without worrying about all the technical details. At least, not to start (smirking).
