This topic provides answers to some frequently asked questions about SQL of fully managed Flink, including errors returned during job development and job O&M.

What do I do if the error message "undefined" appears?

What do I do if the error message "Object '****' not found" appears?

  • Error details
    After you click Run, the error message shown in the following figure appears. Error details
  • Cause

    When you execute DDL and DML statements in the same text, you do not declare CREATE TEMPORARY TABLE in the DDL statement.

  • Solution

    When you execute DDL and DML statements in the same text, you must declare CREATE TEMPORARY TABLE instead of CREATE TABLE in the DDL statement.

What do I do if the error message "Only a single 'INSERT INTO' is supported" appears?

  • Error details
    After you click Run, the error message shown in the following figure appears. Error details
  • Cause

    Multiple DML statements are not written between the key statements BEGIN STATEMENT SET; and END;.

  • Solution

    Write the DML statements between BEGIN STATEMENT SET; and END;. For more information, see DML statement (INSERT INTO).

What do I do if the error message "OSSException" appears?

  • Error details
    The error message appears when a new job is started or a published job is restarted. Error
  • Cause

    Versioning is enabled for OSS, which results in a large number of objects in OSS.

  • Solution
    1. In the OSS console, disable versioning. For more information, see Configure versioning.
    2. Remove all objects from the oss://{bucket}/flink-jobs/namespaces/{namespace}/jobs/ directory.
      ./ossutil64 rm oss://{bucket}/flink-jobs/namespaces/{namespace}/jobs/ --all-versions -r
      Note
      • In this example, ossutil is used to remove the objects. You can also use another method to remove the objects.
      • For more information about the rm command, see rm.
    3. Restart the job of fully managed Flink.

What do I do if the error message "exceeded quota: resourcequota" appears?

  • Error details
    The error message appears when a job is started. Error
  • Cause

    The job fails to be started because the resources of the current project are insufficient.

  • Solution

    You must reconfigure the project resources. For more information, see Reconfigure resources for a single project.

What do I do if the error message "Exceeded checkpoint tolerable failure threshold" appears?

  • Error details
    The error message appears when a job is started. Error details
  • Cause

    The maximum number of checkpoint failures allowed in a task is not specified. By default, a failover is triggered each time a checkpoint fails.

  • Solution
    1. On the right side of the Draft Editor page in the console of fully managed Flink, click the Advanced tab.
    2. In the Additional Configuration section, enter the following parameter:
      execution.checkpointing.tolerable-failed-checkpoints: num
      You must replace num with the number of checkpoint failures that you allow in the task. This parameter must be set to 0 or a positive integer. If the parameter is set to 0, no checkpoint exceptions or failures are allowed.

What do I do if the error message "Flink version null is not configured for sql" appears?

  • Error details
    StatusRuntimeException: INTERNAL: Flink version null is not configured for sql.
  • Cause

    The system is updated to VVR 4.0.8. As a result, the version information about the Flink computing engine of the job cannot be obtained.

  • Solution
    On the right side of the Draft Editor page, click the Advanced tab and select the required version from the Engine Version drop-down list in the Configuration section. Engine version
    Note If you need to use the SQL preview feature, you must check whether the engine version that you selected on the Create Session Cluster page is correct.

What do I do if the error message "java.util.concurrent.CompletionException: java.lang.IllegalArgumentException" appears?

  • Error details
     Caused by: java.util.concurrent.CompletionException: java.lang.IllegalArgumentException: The bucket name "fakeBucket" is invalid. A bucket name must: 1) be comprised of lower-case characters, numbers or dash(-); 2) start with lower case or numbers; 3) be between 3-63 characters long. 
  • Cause

    In the Additional Configuration section of the Advanced tab, the state.backend parameter is configured but the state.checkpoints.dir parameter is not configured.

  • Solution
    If you configure the state.backend parameter, you must configure the state.checkpoints.dir parameter.
    Note You can also delete the state.backend parameter.

What do I do if the error message "INFO: org.apache.flink.fs.osshadoop.shaded.com.aliyun.oss" appears?

  • Error detailsError details
  • Cause

    When OSS creates a directory, it checks whether the directory exists. If the directory does not exist, the error message "INFO: org.apache.flink.fs.osshadoop.shaded.com.aliyun.oss" appears. Flink jobs are not affected.

  • Solution

    Add <Logger level="ERROR" name="org.apache.flink.fs.osshadoop.shaded.com.aliyun.oss"/> to the log template. For more information, see Configure job logs.