Adarsh-Me commented on PR #13566:
URL: https://github.com/apache/ignite/pull/13566#issuecomment-5950191894
@zstan Yes — real SQLLine 1.12.0 against a node started from this branch,
and I also reproduced your screenshot. I compiled `JdbcThinResultSet` from base
`c1bfd5ee` and put it ahead of the patched `ignite-core` on the classpath: same
server, same client, one class different.
| driver class | `isClosed()` right after `getTables()` | `!tables` |
|---|---|---|
| base `c1bfd5ee` | `true` | 0 rows — exactly your paste |
| head `5bb60777` | `false` | 53 rows, incl.
`'IGNITE','TBL_CACHE','ROW','TABLE'` |
```
printf '!tables\n!quit\n' | java --add-opens=java.base/java.util=ALL-UNNAMED
\
-cp
"sqlline-1.12.0-jar-with-dependencies.jar;ignite-core.jar;cache-api.jar" \
sqlline.SqlLine --verbose=true --outputformat=csv --maxWidth=400 \
-u jdbc:ignite:thin://127.0.0.1/ -n sqlline -p sqlline
```
Two things from that. `--outputformat=csv` matters: on a dumb terminal
1.12.0 prints a zero-width grid that looks empty even with 53 rows. And 0 rows
*including every `SYS` view* is what an unpatched `ignite-core` gives, so maybe
your classpath picked up a released jar.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
