dotnet / dotnet/machinelearning-modelbuilder

Data classification: The error message is not very clear after changing the "SentimentText" column's Data type from "String" to "Boolean".

Open
#2,986 0 comments 0 reactions 0 assignees View on GitHub
Priority:2 Reported by: Test
Dominant language
Dockerfile
Stars
285
Forks
66
PR merge metrics
No merged PRs in 30d

Description

**System Information (please complete the following information):**
Windows OS: Windows-11-Enterprise-24H2
ML.Net Model Builder 2022: 17.19.0.2456401 (Main Build)
Microsoft Visual Studio Enterprise: 2022(17.11.5)
.Net: 6.0, 8.0

**Describe the bug**
- On which step of the process did you run into an issue:
The error message is not very clear after changing the "SentimentText" column's Data type to "Boolean".

**TestMatrix**
https://testpass.blob.core.windows.net/test-pass-data/wikipedia-detox-250-line-data.tsv

**To Reproduce**
Steps to reproduce the behavior:
1. Select Create a new project from the Visual Studio start window.
2. Choose the C# Console App (.NET Core) project template.
3. Add model builder by right click on the project.
4. Select "Data classification" scenario.
5. On the Data page, choose the data source, column.
6. Changing the "SentimentText" column's Data type from "String" to "Boolean".
![Image](https://github.com/user-attachments/assets/62c7d75f-3293-4232-af04-0ddc907c3709)
7. On the Train page. click "Start training".
8. Check the error message.

**Expected behavior**
The error message should be like "**Schema mismatch for Context column 'SentimentText': expected String, got Boolean**".

**Screenshot**
![Image](https://github.com/user-attachments/assets/d5f0d8e1-b35d-44a6-81b3-c414adafe771)

**Additional context**
Changing the "SentimentText" column's Data type to "Boolean", actually all data could not be parsed. Because the "context" column's Data type should be "String".
But in the error message it only mentioned the data in line 66.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.