哲平 川口
- Total activity 16
- Last activity
- Member since
- Following 0 users
- Followed by 0 users
- Votes 3
- Subscriptions 5
Activity overview
Latest activity by 哲平 川口-
哲平 川口 created a post,
Other: I really can't believe that support is so lenient on abhering to the OpenAPI schema.
AnsweredI'm talking with the Fivetran support (Enterprise plan), and I'm telling some of them is sometimes violating the OpenAPI schema. Also I'm sending like as following. https://support.fivetran.com/hc/...
-
哲平 川口 commented,
Hello Meera! Thanks for replying, and sorry for late response. It sounds it would work, but I want to limit destructive actions too, and wanna only allow start syncing.
-
哲平 川口 created a post,
Connector Improvement: New Role or Permission to access Sync start.
AnsweredMy team is going to use API in our project. In the application, it is necessary to run Sync connectors manually through API. I quickly confirmed the role which can run Sync is Admin. And Reviewer c...
-
哲平 川口 created a post,
Impersonated Users for API key
PlannedMy team is planning to use multiple API keys based on customers in the application, but all API Key now must be associated with one user.In the first phase, we'll make Google Workspace Group for im...
-
哲平 川口 commented,
Hi Jimmy. Thanks for replying! Are you just generating an Typescript SDK for your use? Yes! In my team, we're evaluating Fivetran for the product. I'm using https://github.com/astahmer/ope...
-
哲平 川口 commented,
I found other problems. Around line 7913 (same for 7988, 8047), written as " AWS_EU_WEST_2", it starts with single space. "region": { "type": "string", "descript...
-
哲平 川口 created a post,
Other: API: Needs Fix: OpenAPI schema definition's all response object properties are OPTIONAL
CompletedWe can download OpenAPI schema from https://developers.fivetran.com/openapi/reference/v1/overview/ `properties` of JSON schema is OPTIONAL by default and if it is REQUIRED, it is necessary to add...
-
哲平 川口 created a post,
Transformations: Transformation Improvement: Record version (like git commit hash) of each run.
Actual: Cannot get version of transformation (dbt repository's version) from run history. Expected: Record version (like git hash commit) internally and can see version in history. Why: It's impo...