-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Fix bug in TextLoader #3011
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Fix bug in TextLoader #3011
Changes from 1 commit
Commits
Show all changes
19 commits
Select commit
Hold shift + click to select a range
7f4e341
Fix bug in TextLoader
yaeldMS 1a89468
Clean FeatureContributionCalculation and PermutationFeatureImportance…
artidoro aea88dc
Updating LightGBM Arguments (#2948)
singlis 8b1b14f
Hiding of ColumnOptions (#2959)
artidoro f03c49d
Updating the FunctionalTests to clearly explain why they are not stro…
eerhardt 00a5b35
Added samples for tree regression trainers. (#2999)
fd1c700
Cleanup the statistics usage API (#2048)
sfilipi de5d48a
Refactor cancellation mechanism and make it internal, accessible via …
codemzs c38f81b
Add functional tests for ONNX scenarios (#2984)
rogancarr 3af9a5d
Make Multiclass Linear Trainers Typed Based on Output Model Types. (#…
wschin 807d813
Clean up the SchemaDefinition class (#2995)
yaeldMS c8a4c7d
Data catalog done (#3021)
sfilipi ce56462
Activate OnnxTransform unit tests for MacOS (#2695)
jignparm e00d19d
Added tests for text featurizer options (Part1). (#3006)
zeahmed a2d7987
Binary FastTree/Forest samples using T4 templates. (#3035)
77be9d9
Polish standard trainers' catalog (Just rename some variables) (#3029)
wschin 5b22420
Polish train catalog (renaming only) (#3030)
wschin ce7f0fb
Merge branch 'tryparseschema' of https://github.com/yaeldekel/machine…
yaeldMS 62dda6f
Add more checks for the syntax of the embedded TextLoader options
yaeldMS File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we explain this change? As far as I can tell, we're considering not finding this loader in the component factory to be no longer an error condition. This may be right, but I'd feel a bit more comfortable with this change if we can explain why?
I did read the attached issue, but it was a little vague on precisely why removing this check is a right and desirable thing to do.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems that this check was there in order to make sure that the schema defined in the file has the correct syntax for creating a legacy TextLoader. The schema defined in the file should always be in the format
TextLoader{col=... }
, since it is generated by theTextSaver
. Instead of the check that I deleted, should we check thatloader.Name==TextLoader.LoaderSignature
?In reply to: 267105243 [](ancestors = 267105243)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since it is a text file, might be manually altered after saving it with the TextSaver?
In reply to: 267424076 [](ancestors = 267424076,267105243)