Heavy Bug working with Primary-Keys/ ID's with 19 digits

[Ylreeb]

Having several issues when dealing with values having 19 digits (in my case Primary-Keys/ ID's) - especially when formated as "Whole Number" (Int64):

- retrieval won't work

- cardinality/data model won't work

- Exporting queries/tables via R script scrambled values

Figured out formating these values as "Type.text" helped within PBI.

For exporting values to a MySQL DB with an easy R-script I had to add an aditional chars (as a workaround) outherwise values got somekind of scrambled or cut of according to the used var typ (on PBI and DB side).

Lookes like a bug to me

[v-qiuyu-msft]

Hi @Ylreeb,

Would you please share T-SQL for us to recreate the sample table on MYSQL side so we can try to reproduce the issue? 

Best Regards,
Qiuyun Yu 

[Ylreeb]

do you mean the statement to create the table?

CREATE TABLE `mam_vizone_daily_tracking_clone` (
  `itm_id` varchar(255) DEFAULT NULL,
  `itm_site_id_str` varchar(255) DEFAULT NULL,
  `itm_title` varchar(255) DEFAULT NULL,
  `itm_ingest_ts` datetime DEFAULT NULL,
  `itm_keyword_cache` varchar(255) DEFAULT NULL,
  `itm_material_type` varchar(255) DEFAULT NULL,
  `sportssport` int(11) DEFAULT NULL,
  `min_file_size` int(32) DEFAULT NULL,
  `_refreshdate` datetime DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8

But you can recap that issue taking a table with one column of values having 19 digits and around 30k rows and  then try filtering to a paritcular value that is not cached (1k rows) setting the "Type" to int64 compaired to text type.