Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Getting Started > Java / Groovy Quickstart #5

Closed
margaretkennedy opened this issue Jan 8, 2024 · 4 comments
Closed

Getting Started > Java / Groovy Quickstart #5

margaretkennedy opened this issue Jan 8, 2024 · 4 comments
Assignees
Labels
update An update to existing documentation

Comments

@margaretkennedy
Copy link
Collaborator

margaretkennedy commented Jan 8, 2024

PR: https://github.com/deephaven/deephaven.io/pull/3921

@margaretkennedy margaretkennedy added documentation update An update to existing documentation labels Jan 8, 2024
@margaretkennedy margaretkennedy added this to the January 2024 (EOM) milestone Jan 8, 2024
@margaretkennedy margaretkennedy changed the title UPDATE: Java / Groovy Quickstart Getting Started > Java / Groovy Quickstart Jan 9, 2024
@stanbrub
Copy link

stanbrub commented Apr 29, 2024

@margaretkennedy In making a Groovy version of this Quickstart guide, there are links to other markdown files that the Python version has, but the Groovy version does not. Is making these markdown files for Groovy part of this exercise, or is that being handled elsewhere? (Example below.)

../how-to-guides/data-import-export/csv-import.md), [Parquet files](../how-to-guides/data-import-export/parquet-single.md

It looks like many of the needed groovy markdown files are there, just not in the same directory structure as the Python markdown.

@margaretkennedy
Copy link
Collaborator Author

@margaretkennedy In making a Groovy version of this Quickstart guide, there are links to other markdown files that the Python version has, but the Groovy version does not. Is making these markdown files for Groovy part of this exercise, or is that being handled elsewhere? (Example below.)

../how-to-guides/data-import-export/csv-import.md), [Parquet files](../how-to-guides/data-import-export/parquet-single.md

It looks like many of the needed groovy markdown files are there, just not in the same directory structure as the Python markdown.

No, we will add any missing content separately! CSV should be there, but we're working on Parquet and Kafka down the line.

@stanbrub
Copy link

@margaretkennedy I really am going down a rat hole here with links in this document. Much of this is caused by the last section that points users to the How-To Guide. Is it really necessary to list all these links like this? Is there no way to reference the root of said How-To Guide. I'm up to 21 added/changed Groovy files and directories with more on the way. Many of those will need to be converted from python, because there was no Groovy counterpart.

- [Import CSV files](../how-to-guides/data-import-export/csv-import.md)
- [Write and read Parquet files](../how-to-guides/data-import-export/parquet-single.md)
- [Connect to a Kafka stream](../how-to-guides/data-import-export/kafka-stream.md)
- [Execute SQL Queries](../how-to-guides/data-import-export/execute-sql-queries.md)
- [Create and organize notebooks using the File Explorer](/core/docs/how-to-guides/user-interface/file-explorer/)
- [Create plots without writing queries using the Chart Builder](/core/docs/how-to-guides/user-interface/chart-builder/)
- [Filter your data without writing queries](/core/docs/how-to-guides/user-interface/filters/)
...

@stanbrub
Copy link

@margaretkennedy In making a Groovy version of this Quickstart guide, there are links to other markdown files that the Python version has, but the Groovy version does not. Is making these markdown files for Groovy part of this exercise, or is that being handled elsewhere? (Example below.)

../how-to-guides/data-import-export/csv-import.md), [Parquet files](../how-to-guides/data-import-export/parquet-single.md

It looks like many of the needed groovy markdown files are there, just not in the same directory structure as the Python markdown.

No, we will add any missing content separately! CSV should be there, but we're working on Parquet and Kafka down the line.

So do I just leave broken links with a comment around them?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
update An update to existing documentation
Projects
None yet
Development

No branches or pull requests

2 participants