}`,
		},
		{
			name:       "limit-2",
			query:      `select * from s3object[*].person[*] limit 1`,
			wantResult: `{"Id":1,"Name":"Anshu","Address":"Templestowe","Car":"Jeep"}`,
			withJSON:   `{ "person": [ { "Id": 1, "Name": "Anshu", "Address": "Templestowe", "Car": "Jeep" }, { "Id": 2, "Name": "Ben Mostafa", "Address": "Las Vegas", "Car": "Mustang" }, { "Id": 3, "Name": "Rohan Wood", "Address": "Wooddon", "Car": "VW" } ] }`,
		},
		{

### Target language

Translate to Portuguese (Português).

Language code: pt.

For instructions or titles in imperative, keep them in imperative, for example "Import FastAPI" to "Importe o FastAPI".

Keep existing translations as they are if the term is already translated.

* mount (verb): монтировать
* mount (noun): точка монтирования / mount (keep in English if it's a FastAPI keyword)
* plugin: плагин
* plug-in: плагин
* full stack: full stack (do not translate)
* full-stack: full-stack (do not translate)
* loop (as in async loop): цикл событий
* Machine Learning: Машинное обучение
* Deep Learning: Глубокое обучение
* callback hell: callback hell (clarify as `ад обратных вызовов`)

* back and forth: de un lado a otro
* I/O (as in "input and output"): I/O (do not translate to "E/S")
* Machine Learning: Machine Learning (do not translate to "Aprendizaje Automático")
* Deep Learning: Deep Learning (do not translate to "Aprendizaje Profundo")
* callback hell: callback hell (do not translate to "infierno de callbacks")
* tip: Consejo (do not translate to "tip")

Language code: ko.

### Grammar and tone

1) Use polite, instructional Korean (e.g. 합니다/하세요 style).
2) Keep the tone consistent with the existing Korean FastAPI docs.

### Headings

1) Follow existing Korean heading style (short, action-oriented headings like “확인하기”).
2) Do not add trailing punctuation to headings.

### Quotes

1) Keep quote style consistent with the existing Korean docs.

3) Keep heading punctuation as in the source. In particular, keep occurrences of literal « - » (space-hyphen-space) as « - » (the existing French docs use a hyphen here).

### French instructions about technical terms

### Target language

Translate to Japanese (日本語).

Language code: ja.

### Grammar and tone

1) Use polite, instructional Japanese (です/ます調).
2) Keep the tone concise and technical (match existing Japanese FastAPI docs).

### Headings

1) Follow the existing Japanese style: short, descriptive headings (often noun phrases), e.g. 「チェック」.
2) Do not add a trailing period at the end of headings.

### Quotes

    }

    @Keep
    protected void protectedOneArg(String s) {
      checkNotNull(s);
    }

    @Keep
    public void oneNullableArg(@Nullable String s) {}

    @Keep
    public void oneNullableArgThrows(@Nullable String s) {
      doThrow(s);
    }

    @Keep
    public void twoArg(String s, Integer i) {
      checkNotNull(s);
      i.intValue();
    }

    @Keep

### Quotes and punctuation

1) Keep punctuation style consistent with existing Traditional Chinese docs (they often mix English terms like “FastAPI” with Chinese text).
2) Never change punctuation inside inline code, code blocks, URLs, or file paths.
3) For more details, please follow the [Chinese Copywriting Guidelines](https://github.com/sparanoid/chinese-copywriting-guidelines).

### Ellipsis

import com.google.common.collect.testing.features.FeatureUtilTest.ExampleFeature.NotTesterAnnotation;
import com.google.common.collect.testing.features.FeatureUtilTest.ExampleFeature.Require;
import com.google.errorprone.annotations.Keep;
import java.lang.annotation.Inherited;
import java.lang.annotation.Retention;
import java.lang.reflect.Method;
import java.util.Set;
import junit.framework.TestCase;

/**
 * @author George van den Driessche