Skip to content

Commit 4c6b2ad

Browse files
tutorials update for use of PyPi install
1 parent 77058c3 commit 4c6b2ad

File tree

4 files changed

+30
-26
lines changed

4 files changed

+30
-26
lines changed

tutorial/1-Introduction.py

Lines changed: 15 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -5,26 +5,21 @@
55

66
# MAGIC %md ### First Steps ###
77
# MAGIC
8-
# MAGIC You will need to import the data generator library to workspace in order to use it. You can find the latest releases in the [``dbldatagen``](https://github.com/databrickslabs/dbldatagen) github repository
9-
# MAGIC on the [releases pane](https://github.com/databrickslabs/dbldatagen/releases)
10-
# MAGIC
11-
# MAGIC Download the wheel for the latest release from there.
12-
# MAGIC
13-
# MAGIC Steps:
14-
# MAGIC 1. In your Databricks environment, using the left hand pane to select your workspace, create a library entry
15-
# MAGIC for the test data generator library
16-
# MAGIC 1. if there's an older library already installed:
17-
# MAGIC 1. uninstall it from existing clusters that it is installed on
18-
# MAGIC 9. restart the cluster(s) to have the uninstall take effect
19-
# MAGIC 9. move the library to trash
20-
# MAGIC 9. use the create option for the workspace folder
21-
# MAGIC 9. select library
22-
# MAGIC 9. select Python Wheel library type (by setting the library type option to `python whl`)
23-
# MAGIC 9. Once the library reference is created, you can install it on your clusters. You may need to restart them
24-
# MAGIC to take effect
25-
# MAGIC
26-
# MAGIC 9. You can now refer to the library in your notebooks. Note the library is a Python 3 wheel library and
27-
# MAGIC must be run on a compatible cluster
8+
# MAGIC You will need to import the data generator library in order to use it.
9+
# MAGIC
10+
# MAGIC Within a notebook, you can install the package from PyPi using `pip install` to install the
11+
# MAGIC package with the folling command:
12+
# MAGIC
13+
# MAGIC ```
14+
# MAGIC %pip install dbldatagen
15+
# MAGIC ```
16+
# MAGIC
17+
# MAGIC The [Installation Notes](https://databrickslabs.github.io/dbldatagen/public_docs/installation_notes.html)
18+
# MAGIC provides details on other mechanisms for installation.
19+
20+
# COMMAND ----------
21+
22+
# MAGIC %pip install dbldatagen
2823

2924
# COMMAND ----------
3025

tutorial/2-Basics.py

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,6 @@
11
# Databricks notebook source
2-
# MAGIC %md ### Using the Databricks Labs Data Generator ###
3-
# MAGIC
4-
# MAGIC #### Setup ####
5-
# MAGIC Import the Data Generator library wheel file into your environment and attach to cluster being used to
6-
# MAGIC run notebook
2+
# DBTITLE 1,Install package from PyPi
3+
# MAGIC %pip install dbldatagen
74

85
# COMMAND ----------
96

tutorial/3-ChangeDataCapture-example.py

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,9 @@
11
# Databricks notebook source
2+
# DBTITLE 1,Install package from PyPi
3+
# MAGIC %pip install dbldatagen
4+
5+
# COMMAND ----------
6+
27
# MAGIC %md ###Change Data Capture
38

49
# COMMAND ----------

tutorial/4-Generating-multi-table-data.py

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,9 @@
11
# Databricks notebook source
2+
# DBTITLE 1,Install package from PyPi
3+
# MAGIC %pip install dbldatagen
4+
5+
# COMMAND ----------
6+
27
# MAGIC %md ##Multi table data generation
38
# MAGIC
49
# MAGIC To illustrate multi-table data generation and use, we'll use a simplified version of telecoms billing processes.
@@ -24,7 +29,9 @@
2429
# MAGIC
2530
# MAGIC Messages will be priced per actual counts
2631
# MAGIC
27-
# MAGIC For simplicitity, we'll ignore the free data, messages and calls threshold in most plans and the complexitity of matching devices to customers and telecoms operators - our goal here is to show generation of join ready data, rather than full modelling of phone usage invoicing.
32+
# MAGIC For simplicitity, we'll ignore the free data, messages and calls threshold in most plans and the complexity
33+
# MAGIC of matching devices to customers and telecoms operators - our goal here is to show generation of join
34+
# MAGIC ready data, rather than full modelling of phone usage invoicing.
2835

2936
# COMMAND ----------
3037

0 commit comments

Comments
 (0)