// {{ TEMPLATE: }}
module.exports = {
LATEST_RELEASE: {
type: 'customQuery',
loop: false,
query: async (octokit, moment, user) => {
// You can do anything you want with the GitHub API here.
const result = await octokit.graphql(`
query {
repository(name: "spark-clickhouse-plugin", owner: "The-Analytics-Gladiators") {
refs(refPrefix: "refs/tags/", last: 1) {
edges {
node {
name
}
}
}
}
}
`)
const release = result.repository.refs.edges[0].node
// We have `loop: false`, so we return an object.
// If we had `loop: true`, we would return an array of objects.
return {
RELEASE_TAG: release.name.replace("v", "")
}
}
}
}
// {{ :TEMPLATE }}
Behold the most intuitive Spark Plugin for interacting with Clickhouse
<profiles>
<profile>
<id>github</id>
<repositories>
<repository>
<id>jitpack.io</id>
<url>https://jitpack.io</url>
</repository>
</repositories>
</profile>
</profiles>
<dependencies>
<dependency>
<groupId>com.github.The-Analytics-Gladiators</groupId>
<artifactId>spark-clickhouse-plugin_2.12</artifactId>
<version>{{ RELEASE_TAG }}</version>
</dependency>
</dependencies>
resolvers += "jitpack" at "https://jitpack.io"
libraryDependencies += "com.github.The-Analytics-Gladiators" % "spark-clickhouse-plugin" % "{{ RELEASE_TAG }}"
Contributions are welcome, but there are no guarantees that they are accepted as such. Process for contributing is the following:
- Fork this project
- Create an issue to this project about the contribution (bug or feature) if there is no such issue about it already. Try to keep the scope minimal.
- Develop and test the fix or functionality carefully. Only include minimum amount of code needed to fix the issue.
- Refer to the fixed issue in commit
- Send a pull request for the original project
- Comment on the original issue that you have implemented a fix for it
Spark Clickhouse Plugin is licensed under the MIT license. See the LICENSE.txt file for more information.