Skip to content

Updating/fixing mapr-streams-sample-python to work with new version mapr-streams-python 2.6.0 #3

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

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

archanapujar
Copy link

In this pull request we are fixing

  1. mapr-streams-sample-python to work with new verion mapr-streams-python 2.6.0 that will be released in 7.10.0 + EEP 9.4.0.
  2. Changing all instances of MapR to HPE Data Fabric in the README file.

TODO in the next commit:
I will fix the links in the README file to the the 7.10 docs. This will be done once the 7.10.0 docs are published.

1. To start, you need to get a **MapR 5.2** running. You can install your [own cluster](https://mapr.com/download/) or [download a sandbox](https://mapr.com/products/mapr-sandbox-hadoop/download/).
* **NOTE**: In this example, we used the MapR 5.2 Sandbox via VirtualBox.
2. Your MapR test node or local machine running these Python scripts must have **Python 3.6**
1. To start, you need to get a **HPE Data Fabric 7.10 with EEP 9.4.0** running. You can install your [own cluster](ihttps://docs.ezmeral.hpe.com/datafabric-customer-managed/79/install.html) or [download a sandbox](https://docs.ezmeral.hpe.com/datafabric-customer-managed/79/MapRContainerDevelopers/RunMapRContainerDevelopers.html?hl=sandbox).

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(ihttps://docs.ezmeral.hpe.com/datafabric-customer-managed/79/install.html) change this to (https://docs.ezmeral.hpe.com/datafabric-customer-managed/79/install.html)

Copy link

@prasanna46dk prasanna46dk Apr 8, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

extra i is added at the beginning of link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

JFYI - Doc links can have home instead of the version in the URL to default to the latest release documentation
example: https://docs.ezmeral.hpe.com/datafabric-customer-managed/home/install.html

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @prasanna46dk and @rohanjayaraj . I will change this in the next commit after verifying with latest 7.10 urls.

2. Your MapR test node or local machine running these Python scripts must have **Python 3.6**
1. To start, you need to get a **HPE Data Fabric 7.10 with EEP 9.4.0** running. You can install your [own cluster](ihttps://docs.ezmeral.hpe.com/datafabric-customer-managed/79/install.html) or [download a sandbox](https://docs.ezmeral.hpe.com/datafabric-customer-managed/79/MapRContainerDevelopers/RunMapRContainerDevelopers.html?hl=sandbox).
* **NOTE**: In this example, we used the HPE Data Fabric 7.10 with EEP 9.4.0 cluster.
2. Your HPE Data Fabric test node or local machine running these Python scripts must have **Python 3.11**

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think so we have dependency on python 3.11 anymore, do we?

Copy link
Author

@archanapujar archanapujar Apr 8, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't have a dependency on the version. We are just picking 3.11 version here, like we did with 3.6 in the previously published demo example.

3. Create and activate a Python **virtualenv** in either Mac OS X or Linux
```
$ python3.6 -m venv --system-site-packages ~/maprstreams
$ python3.11 -m venv --system-site-packages ~/maprstreams

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we can use python3 instead

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we use Python 3 we will not know if they have lower versions of Python that we have not tested/support. So using 3.11 as an example like 3.6.

@@ -1,5 +1,5 @@
#!/usr/bin/env python3

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if we are forcing customer to use 3.11 then this line should be. #!/usr/bin/env python3.11

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We are not forcing them to use 3.11, we are just suggesting to use 3.11 for example purpose.

I will add a note in the readme that mapr-streams-python version 2.6.0 is qualified on 3.7 to 3.12. We are using 3.11 as an example here. Does that sound right @prasanna46dk?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, that will help.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@prasanna46dk Thank you! I will add that info.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants