This package is identified as a plugin for the FABRIC SDK, specifically designed for use within Microsoft Fabric's online Spark/Python Notebook environments and Spark Job Definitions (SJDs). It appears to be an internal component that enables or integrates analytics capabilities within the broader Fabric platform, rather than a library intended for direct user-level imports and interactions. Microsoft Fabric is an end-to-end data analytics platform offering data engineering, data science, data warehousing, and real-time analytics. The current version is 0.0.3.post4.
pip install fabric-analytics-notebook-pluginNo compatibility data collected yet for this library.
This quickstart demonstrates common patterns for interacting with data and built-in utilities within a Microsoft Fabric Python Notebook environment, as the `fabric-analytics-notebook-plugin` itself is not designed for direct user-level imports. It shows how to read data using PySpark and how to use the `notebookutils` (formerly `mssparkutils`) package to interact with the file system, which are core operations in Fabric analytics workflows.
Users should focus on using the standard Fabric notebook capabilities, including PySpark, Python libraries, and the built-in `notebookutils` package, rather than attempting to directly import this plugin.
Update imports from `from mssparkutils import ...` to `from notebookutils import ...` and adopt `notebookutils` for all new development to ensure future compatibility and access to new features.
Regularly save your notebooks. Configure session timeout durations in Workspace settings under 'Data Engineering/Science Spark settings' if you have the necessary permissions. Be aware of capacity limits that might pause your workspace.
Ensure that all necessary dependencies are explicitly added to your custom Fabric environment, or switch to the 'Workspace Default' environment which typically includes all core Fabric-specific components. If using a custom environment, verify that its `fsspec` version is compatible with the Fabric runtime and other installed libraries.
Instead of using `%pip install` within the notebook, manage your Python libraries by creating a 'Managed Fabric Environment' and attaching it to your notebook or pipeline activity. This pre-installs dependencies before execution, ensuring a stable and reproducible environment.
Adjust your Spark SQL queries to use single-part namespaces where required by the `spark_catalog`. For instance, when creating a schema, use `CREATE SCHEMA IF NOT EXISTS schema_name` instead of `CREATE SCHEMA IF NOT EXISTS lakehouse_name.schema_name` if the context is already within the lakehouse.
A common workaround is to change your web browser's language setting to English and then try opening the notebook in VS Code again. Ensure your VS Code extensions, particularly the Fabric/Synapse extension, are updated to the latest version.