awesome-astra/docs

Documentation for awesome Astra

docs's Issues

Update screenshots for Stargate graphQL page

Update screenshots on Create Token page

Update JDBC information for Pentaho

Pentaho uses the old method of downloading the SIMBA JDBC drivers. These drivers are no longer available from DataStax downloads.

We should update the instructions to includes the two options for JDBC

• Using the ING JDBC Drivers (Preferred)
• Opening a DataStax Support ticket to obtain the SIMBA Drivers

Here is an example of using these two options in the DataGrip page https://awesome-astra.github.io/docs/pages/data/explore/datagrip/#using-ing-drivers

Update JDBC information for Liquibase

Liquibase uses the old method of downloading the SIMBA JDBC drivers. These drivers are no longer available from DataStax downloads.

We should update the instructions to includes the two options for JDBC

• Using the ING JDBC Drivers (Preferred)
• Opening a DataStax Support ticket to obtain the SIMBA Drivers

Here is an example of using these two options in the DataGrip page https://awesome-astra.github.io/docs/pages/data/explore/datagrip/#using-ing-drivers

Update screenshots on Create Database page

add Temporal page to Third-Party Tools

From: https://docs.google.com/document/d/1k4Vygbf0OUld8hTPvRmJzpRmqvmdtOzEH_OYHXOTAZo/edit

Update JDBC information for Tableau

Tableau uses the old method of downloading the SIMBA JDBC drivers. These drivers are no longer available from DataStax downloads.

We should update the instructions to includes the two options for JDBC

• Using the ING JDBC Drivers (Preferred)
• Opening a DataStax Support ticket to obtain the SIMBA Drivers

Here is an example of using these two options in the DataGrip page https://awesome-astra.github.io/docs/pages/data/explore/datagrip/#using-ing-drivers

Update JDBC Information for DBSchema

DBSchema uses the old method of downloading the SIMBA JDBC drivers. These drivers are no longer available from DataStax downloads.

We should update the instructions to includes the two options for JDBC

• Using the ING JDBC Drivers (Preferred)
• Opening a DataStax Support ticket to obtain the SIMBA Drivers

Here is an example of using these two options in the DataGrip page https://awesome-astra.github.io/docs/pages/data/explore/datagrip/#using-ing-drivers

Update create account page with new UI

Update screenshots on Streaming Create Topic page

Update with Strapi integration

Update screenshots on Secure Connect Bundle page

Update screenshots for Astra Data Loader integration

Stargate gRPC develop page

In the Develop section of Awesome Astra, we currently provide guides to get started with Document API and REST but are missing a guide to get started with gRPC. This is a tracking issue to follow the progress of the gRPC guide.

Update JDBC information for DBeaver

DBeaver uses the old method of downloading the SIMBA JDBC drivers. These drivers are no longer available from DataStax downloads.

We should update the instructions to includes the two options for JDBC

• Using the ING JDBC Drivers (Preferred)
• Opening a DataStax Support ticket to obtain the SIMBA Drivers

Here is an example of using these two options in the DataGrip page https://awesome-astra.github.io/docs/pages/data/explore/datagrip/#using-ing-drivers

add JanusGraph to Third-Party Tools

Update screenshots on Multi-regions page

Provide a writing guide to ensure consistent tone across pages

Create a readme that will describe a standard tone that we will use for new getting started tutorials, integrations, etc.

Update screenshots in FAQ page

Update Golang gocql docs

What

Golang documentation for gocql driver is outdated and is not working with Cassandra 4.0+ versions nor latest driver versions.

It would be nice to update the documentation to avoid confusion to newcomers.

How

After a research, I've encountered gocql version 1.20 (and potentially lower versions) had a host peer-related function referencing to system.peers_v2 table which is not existent in Cassandra 4.0+ AFAIK. Thus, driver is not able to create a session.

Updating to gocql 1.2.1 fixed this issue while another issue surfaced (x509: cannot validate certificate for because it doesn't contain any IP SANs).

In order to solve this last issue, just add ServerName field to tls.Config struct referencing to host variable defined previously and used as cluster host.

Example:

package main

import (
	"context"
	"crypto/tls"
	"crypto/x509"
	"fmt"
	"os"
	"path/filepath"
	"time"

	"github.com/gocql/gocql"
)

func main() {
	const (
		port = 29042
	)
	var err error

	hostname := "YOUR_DATABASE_ID-YOUR_REGION.db.astra.datastax.com"
	username := "YOUR_CLIENT_ID" // or set as "token" to use secure token strategy
	password := "YOUR_CLIENT_SECRET" // or secure token

	caPath, _ := filepath.Abs("PATH_TO_SECURE_BUNDLE/ca.crt")
	certPath, _ := filepath.Abs("PATH_TO_SECURE_BUNDLE/cert")
	keyPath, _ := filepath.Abs("PATH_TO_SECURE_BUNDLE/key")

	cluster := gocql.NewCluster(hostname)
	cluster.Port = port
	cluster.ProtoVersion = 4
        // set to true to avoid system.peer table fetch and bypass first error (NOT RECOMMENDED)
	//cluster.DisableInitialHostLookup = true

	cluster.Authenticator = gocql.PasswordAuthenticator{
		Username: username,
		Password: password,
	}

	cert, err := tls.LoadX509KeyPair(certPath, keyPath)
	if err != nil {
		panic(err)
	}
	caCert, err := os.ReadFile(caPath)
	if err != nil {
		panic(err)
	}
	caCertPool := x509.NewCertPool()
	ok := caCertPool.AppendCertsFromPEM(caCert)
	if !ok {
		panic("cannot append cert")
	}
	tlsConfig := &tls.Config{
		Certificates: []tls.Certificate{cert},
		RootCAs:      caCertPool,
                // set to true if ServerName field is not populated (NOT RECOMMENDED)
		//InsecureSkipVerify: true,
		ServerName: "YOUR_DATABASE_ID-YOUR_REGION.db.astra.datastax.com",
	}

	cluster.SslOpts = &gocql.SslOptions{
		Config:                 tlsConfig,
		EnableHostVerification: false,
	}

	session, err := cluster.CreateSession()
	if err != nil {
		panic(err)
	}
	defer session.Close()
	ctx := context.Background()

	var strClusterName string
	err2 := session.Query(`SELECT cluster_name FROM system.local`).WithContext(ctx).Scan(&strClusterName)
	if err2 != nil {
		panic(err2)
	} else {
		fmt.Println("cluster_name:", strClusterName)
	}

	duration := time.Duration(10) * time.Second // Pause for 10 seconds
	time.Sleep(duration)
}

Update screenshots on Resume Database page