Serverless

Is your feature request related to a problem? Please describe.

I noticed many problems people have in issues and discussions are caused by the fact that they are not aware that we use caching to reduce the server load.

Describe the solution you'd like

Although this is explained in the README, it is placed under the gradient section (See https://github.com/anuraghazra/github-readm

Is there an existing issue for this?

• I have searched existing issues, it hasn't been reported yet

Use case description

Currently, we have websocket-related properties configured directly on provider level:

• provider.websocketsApiName
• provider.websocketsApiRouteSelectionExpression
• provider.websocketsDescription

This is not consistent with how iam, httpApi or

expected result:
example.com?param=abc -> will become example.com
example.com/?param=abc -> will stay example.com/

actual result:
example.com?param=abc -> become example.com
example.com/?param=abc -> stays example.com/?param=abc

Enhancement

mysql> CREATE TABLE t1 (
    -> risk_id varchar(32) NOT NULL,
    -> tran_id int NOT NULL,
    -> KEY (`risk_id`)
    -> );

mysql> CREATE TABLE t2 (
    -> risk_id varchar(32) COLLATE utf8mb4_general_ci NOT NULL,
    -> -- risk_id varchar(32) NOT NULL,
    -> tran_id int NOT NULL,
    -> KEY (`risk_id`)
    -> );

mysql> explain select /*+ hash_join(t1) */ t1.ris

💭 Description

Even though the upgrade docs state:

You do not need to run migration when upgrading to a minor version. For example, going from 0.13.0 to 0.13.2 would not require running migration.

When following along with the instructions, the "Running the Migration" just says:

We can now start the migration. Navigate to the appwrite directory where your docker-compose.yml is pre

The feature ask - expose Dapr runtime version in the Metadata API: https://docs.dapr.io/reference/api/metadata_api/

There are certain scenarios where apps would like to check that they are running within a tested Dapr version.

Describe the bug
Using a time dimension on a runningTotal measure on Snowflake mixes quoted and unquoted columns in the query. This fails the query, because Snowflake has specific rules about quoted columns. Specifically:

• All unquoted column names are treated as upper case
• Quoted column names are case sensitive.

So "date_from" <> date_from

To Reproduce
Steps to reproduce

Current State

We currently hardcore the APISIX version in the blog or doc, which has misled some newcomers when they read an old blog version. This also makes updating the latest APISIX version in the doc harder, because we need to change several places.

Desired State

Let's add a static file containing the version numbers, and provide a simple one-liner command to get the version numbe

Is your feature request related to a problem? Please describe.

Missing functionality to update min/max cpu/mem of an exiting ENV. Currently, to update, we are forced to delete and re-create the env. This also has a risk of dependent functions being erratic. It also de-couple resource utilization independent of function creation and be useful to update the resource in a quick to respond situ

Version

5.29.0

Operating System

/

Browser

/

What steps will reproduce the bug?

Just try issuing the following mutation, and you should be able to see the error message on the right:

What is the expected behavior?

We