You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/data-integrations/datastax.mdx
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,6 +16,10 @@ The required arguments to establish a connection are as follows:
16
16
*`user` is the user to authenticate.
17
17
*`password` is the password to authenticate the user.
18
18
*`secure_connection_bundle` is the path to the `secure_connection_bundle` zip file.
19
+
<Tip>
20
+
If you installed MindsDB locally via pip, you need to install all handler dependencies manually. To do so, go to the handler's folder (mindsdb/integrations/handlers/datastax_handler) and run this command: `pip install -r requirements.txt`.
Copy file name to clipboardExpand all lines: mindsdb/integrations/handlers/gmail_handler/README.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,14 +9,14 @@ To see how the Gmail handler is used, let's walk through the steps to create a s
9
9
10
10
## Connect to the Gmail API
11
11
12
-
To use the Gmail API we need to setup a Google Cloud Project and a Google Account with Gmail enabled.
12
+
To use the Gmail API we need to set up a Google Cloud Project and a Google Account with Gmail enabled.
13
13
14
14
Before proceeding further, we will need to enable the Gmail API from the Google Cloud Console.
15
15
16
-
We will also need to create OAuth Client Ids for authenticating users, and possibly an Auth Consent Screen (if this is the first time we're setting up OAuth)
16
+
We will also need to create OAuth Client Ids for authenticating users, and possibly an Auth Consent Screen (if this is the first time we're setting up OAuth).
17
17
18
18
Setting up OAuth Client Id will give us a credentials file which we will need in our mindsdb setup. You can find more information on how to do
19
-
this [here](https://developers.google.com/gmail/quickstart/python).
19
+
this [here](https://developers.google.com/gmail/api/quickstart/python).
20
20
21
21
**Optional:** The credentials file can be stored in the gmail_handler folder in
22
22
the `mindsdb/integrations/handlers/gmail_handler` directory.
@@ -33,7 +33,7 @@ parameters = {
33
33
This creates a database called mindsdb_gmail. This database ships with a table called emails that we can use to search for
34
34
emails as well as to write emails.
35
35
36
-
You can also create a database by giving the credentials file from a s3 pre signed url.To do this you need to pass in the credentials_file parameter as a signed url.For example:
36
+
You can also create a database by giving the credentials file from a s3 pre signed url.To do this you need to pass in the credentials_file parameter as a signed url.For example:
37
37
38
38
~~~~sql
39
39
CREATEDATABASEmindsdb_gmail
@@ -59,7 +59,7 @@ LIMIT 20;
59
59
~~~~
60
60
This will search your Gmail inbox for any email which contains the text `alert` and is from `google.com` domain (notice the use of the wildcard `*`).
61
61
62
-
The returned result should have ROWs like this
62
+
The returned result should have ROWs like this,
63
63
64
64
| id | message_id | thread_id | label_ids | sender | to | date | subject | snippet | history_id | size_estimate | body | attachments |
@@ -68,7 +68,7 @@ The returned result should have ROWs like this
68
68
where
69
69
* query - The search term. The query parameter supports all the search terms we can use with gmail. For more details please check [this link](https://support.google.com/mail/answer/7190)
70
70
* label_ids - A comma separated string of labels to search for. E.g. "INBOX,UNREAD" will search for unread emails in inbox, "SENT" will search for emails in the sent folder.
71
-
* include_spam_trash - BOOLEAN (TRUE / FALSE). By default it is FALSE. If included, the search will cover the SPAM and TRASH folders.
71
+
* include_spam_trash - BOOLEAN (TRUE / FALSE). By default, it is FALSE. If included, the search will cover the SPAM and TRASH folders.
72
72
73
73
## Writing Emails
74
74
@@ -112,7 +112,7 @@ USING
112
112
input_column ='text_spammy',
113
113
labels = ['ham', 'spam'];
114
114
~~~~
115
-
* Then you can have to create a view of the email table that contains the snippet or the body of the email.For example by using the snippet:
115
+
* Then you can have to create a view of the email table that contains the snippet or the body of the email.For example by using the snippet:
0 commit comments