Skip to content

Commit e6b945f

Browse files
authored
Update how-to-migrate-from-v1.md
1 parent 8343186 commit e6b945f

File tree

1 file changed

+0
-9
lines changed

1 file changed

+0
-9
lines changed

articles/machine-learning/how-to-migrate-from-v1.md

Lines changed: 0 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -35,15 +35,6 @@ You should use v2 if you're starting a new machine learning project or workflow.
3535

3636
A new v2 project can reuse existing v1 resources like workspaces and compute and existing assets like models and environments created using v1.
3737

38-
Some feature gaps in v2 include:
39-
40-
- Spark support in jobs - currently in preview in v2.
41-
- Publishing jobs (pipelines in v1) as endpoints. You can however, schedule pipelines without publishing.
42-
- Support for SQL/database datastores.
43-
- Ability to use classic prebuilt components in the designer with v2.
44-
45-
You should then ensure the features you need in v2 meet your organization's requirements, such as being generally available.
46-
4738
> [!IMPORTANT]
4839
> New features in Azure Machine Learning will only be launched in v2.
4940

0 commit comments

Comments
 (0)