Skip to content
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

Setup only clickhouse backend #984

Open
b17k0 opened this issue Nov 13, 2024 · 6 comments
Open

Setup only clickhouse backend #984

b17k0 opened this issue Nov 13, 2024 · 6 comments
Labels
customer feedback enhancement New feature or request

Comments

@b17k0
Copy link
Contributor

b17k0 commented Nov 13, 2024

Hello! Is it possible to set up quesma without elasticsearch?
I mean, to have the following scheme: Kibana -> Quesma -> ClickHouse
With this configuration:

#licenseKey: {your-quesma-license-key-if-needed} # license key is required for paid features such as `hydrolix` backend conector
frontendConnectors:
  - name: elastic-query
    type: elasticsearch-fe-query
    config:
      listenPort: 8080
backendConnectors:
  - name: my-clickhouse-data-source
    type: clickhouse-os
    config:
      url: "clickhouse://localhost:9000"
      adminUrl: "http://localhost:8123/play"
ingestStatistics: true
disableTelemetry: true
logging:
  path: "logs"
  level: "info"
  disableFileLogging: false
processors:
  - name: my-query-processor
    type: quesma-v1-processor-query
    config:
      indexes:
        some_transactions:
          target: [ my-clickhouse-data-source ]
          schemaOverrides:
            fields:
              timestamp:
                type: alias
                targetColumnName: "started_at"
              id:
                type: "keyword"
              started_at:
                type: "date"
              uuid:
                type: "keyword"
              account_id:
                type: "keyword"
              state:
                type: "keyword"
              category:
                type: "keyword"
              balance_at_start:
                type: "float"
              balance_at_end:
                type: "float"
              finished_at:
                type: "date"
              currency_id:
                type: "keyword"
              merchant_id:
                type: "keyword"
              user_login:
                type: "keyword"
              # more fields
        "*":       # DO NOT remove, always required
          target: [ my-clickhouse-data-source ]
pipelines:
  - name: my-pipeline-elasticsearch-query-clickhouse
    frontendConnectors: [ elastic-query ]
    processors: [ my-query-processor ]
    backendConnectors: [ my-clickhouse-data-source ]

I get the following error:

2024/11/13 15:51:54 Config validation failed: 2 errors occurred:
	* pipeline my-pipeline-elasticsearch-query-clickhouse has a processor of type quesma-v1-processor-query which requires having one elasticsearch backend connector
	* query processor requires two backend connectors
@ptbrzoska
Copy link
Contributor

Hi, thanks for you question, Quesma always requires a minimal Elasticsearch/OpenSearch cluster for:

  • storing Kibana/OSD metadata
  • storing user data and authentication (unless its explicitly disabled)
  • storing any additional indexes appearing at ingest endpoint and not explicitly listed in Quesma ingest processor
    no data needs to reside there though, everything can be in ClickHouse. Check this page for more information: https://docs.quesma.com/example-2-0-clickhouse-specific.html

@b17k0
Copy link
Contributor Author

b17k0 commented Nov 13, 2024

Thank you for the answer. Is it possible to add a processor type where elasticsearch is not needed?
That is, to store data such as Kibana/OSD metadata, storing user data, in a separate clickhouse table?
I'm looking for options to connect kibana to clickhouse, but I really don't want to keep even minimal elasticsearch.

@ptbrzoska
Copy link
Contributor

Understood. That's currently a roadmap item - feel free to come back in some time to check if that's available in one of the next releases.

@ptbrzoska ptbrzoska added enhancement New feature or request customer feedback labels Nov 13, 2024
@mieciu
Copy link
Member

mieciu commented Nov 20, 2024

Closing for now as this is going to be a part of way bigger initiative.

Thank you for your feedback and detailed explanation, it is truly appreciated! ❤️

At this moment, we do not have publicly-facing roadmap for people to follow, so I'd encourage you to subscribe to our newsletter (there's form at the bottom of this page) to stay up to date with the project!

@mieciu mieciu closed this as completed Nov 20, 2024
@avelanarius avelanarius closed this as not planned Won't fix, can't repro, duplicate, stale Nov 20, 2024
@avelanarius
Copy link
Member

Changed the closing reason from "completed" to more appropriate "not planned" (not planned in the short term)

@avelanarius avelanarius reopened this Nov 20, 2024
@ptbrzoska
Copy link
Contributor

Mistake. Re-opened

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer feedback enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants