> For the complete documentation index, see [llms.txt](https://zjffdu.gitbook.io/flink-on-zeppelin/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zjffdu.gitbook.io/flink-on-zeppelin/configure-flink-interpreter.md). # Configure Flink Interpreter There're 2 approaches to configure flink interpreter * Global setting in interpreter page * Note level setting ## Global Setting The setting in interpreter page is global, any change in interpreter page would affect all the notes. So it is suitable to configure global setting such as `FLINK_HOME`，`HADOOP_CONF_DIR`, `HIVE_CONF_DIR`, `zeppelin.pyflink.python` ![](https://3876819094-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MEawVq7dzi4LX1-ifgT%2F-MG6sBvOFrtL10Yd9GSB%2F-MG7CoFtyblswPb1cUeG%2Fimage.png?alt=media\&token=a882ecbe-4185-4bea-88e4-442e3a044c28) ## Note Level Setting Note level setting only works when the interpreter binding mode is `isolated per note`. Usually you put the note level setting in the first paragraph via `%flink.conf` It is suitable to customize flink interpreter via note level setting such as `flink.execution.packages`, `flink.udf.jars`, `flink.yarn.appName`. Note level setting takes precedence over the global setting in interpreter page. e.g. You can set `FLINK_HOME` in `%flink.conf` to override that in interpreter setting page. Here's one simple example. ![](https://3876819094-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MEawVq7dzi4LX1-ifgT%2F-MG6sBvOFrtL10Yd9GSB%2F-MG7D-7Z-ay0Il15-5bi%2Fimage.png?alt=media\&token=dfd1c1bd-a51b-4dfd-aba7-05f11c9324ac) ## Community Join Zeppelin community to discuss with others {% embed url="" %}