Skip to main content

MQTT Extractor - Notes & Feedback

  • November 21, 2023
  • 5 replies
  • 60 views
N
Seasoned

While testing the hosted MQTT extractor and the pre-release front end I have noted a couple of things you might be interested in, but I’m also guessing some of these are quite obvious to you and already in the pipeline. 

  1. Front end should support creating a new destination with specified dataset.
  2. Viewing and editing a stream transformation without deleting and creating a new one would be nice.
  3. A way of listing existing transformation mappings and create or draft new ones without setting up an extractor instance for it would be helpful.
  4. Transform error-messages might not point at correct line and character in the message it returns.
    • I don't have an example of this right now, I will post one if I see it again.
  5. Transformation Mappings entity could have a description-attribute that lets users describe the scenario it is written created for.
  6. The endpoint listed in beta docs for creating destinations did not work, I ended up using the same endpoint as the front-end where "hostedextractors" is instead "pluto".
  7. When we tried the check operators for Kuiper listed here, "float" and "number" did not work.

5 replies

E
Practitioner
  • Einar Omang
  • Practitioner
  • November 21, 2023

1, 2, 3 are planned. I know there are cases of 4, any examples you can give are helpful, we’ll talk about 5. 6 may be a real issue, we will look into it. 7 is a documentation issue actually, try removing the quotes around `”float”` and `”number”`. The frontend might not properly reflect that change yet, we’ll get to it soon.

Thanks for the feedback.

E
Practitioner
  • Einar Omang
  • Practitioner
  • November 21, 2023

hostedextractors works fine for me, did you add the `cdf-version: beta` header?

 

Avoid relying on `pluto`, it isn’t intended for public consumption and will be removed soon.

N
Seasoned
  • Nicolai
  • Author
  • Seasoned
  • November 21, 2023

hostedextractors works fine for me, did you add the `cdf-version: beta` header?

I believe I tried both beta and alpha, but I don’t have the request so cannot be too sure. If it works for you I guess I must have missed something else, all good. 

Avoid relying on `pluto`, it isn’t intended for public consumption and will be removed soon.

That makes sense, we’re still in a testing phase.

    D

    hostedextractors works fine for me, did you add the `cdf-version: beta` header?

     

    Avoid relying on `pluto`, it isn’t intended for public consumption and will be removed soon.

    I started testing this myself and I had the same issue with the alpha / beta header not working. But I discovered that this is an issue with the documentation. It states to use the date version number "cdf-version: 20230101-alpha", but the correct header was as you said "cdf-version: alpha".
    https://api-docs.cognite.com/20230101/#section/API-versions/Alpha-versions

    E
    Practitioner
    • Einar Omang
    • Practitioner
    • December 5, 2023

    Huh, that’s right, we’ve changed this on a company wide basis recently. We’ll look into it. You can keep using just `alpha` it will continue to work.

      Terms & ConditionsCookie SettingsAccessibility statement