cockroach-staging hello-world issues

cockroach-staging / hello-world

0 stars 0 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

S424:

#623 exalate-issue-sync[bot] opened 4 years ago
0
S48: As an admin, I want to see if there is anything happening on a particular node (or collection of nodes via a rollup), so I know if I need to take some action.

#622 exalate-issue-sync[bot] opened 4 years ago
1
S290: As a DBA, I want to make sure that any streaming pipeline I set up does not significantly adversely impact my existing live production systems so that I can continue to provide live applications with their expected SLAs

#621 exalate-issue-sync[bot] opened 4 years ago
1
S161: As a developer, I want to be able to query based on location so that my application (e.g., Uber) can use location data in its function

#620 exalate-issue-sync[bot] opened 4 years ago
0
S163: As a developer, I want to be able to name the partition scheme for a partition table and reuse it across multiple other tables so that I can save time in partitioning my tables and so that I can avoid user error. For example, if I had a table t (...

#619 exalate-issue-sync[bot] opened 4 years ago
1
S425: As a developer, I want to migrate data from a non managed CockroachDB cluster to a managed CockroachDB cluster so that I can upgrade an older non managed cluster to the latest release the managed cluster is running on.

#618 exalate-issue-sync[bot] opened 4 years ago
1
S286: As a CRDB PM, I want to know that we have tested running CRDB using the local persistent volume options in K8s so that our customers have a storage option outside of EBS that is bug free.

#617 exalate-issue-sync[bot] opened 4 years ago
0
S30: As an operator, I want to be able to see multiple clusters with a single login so that I can manage my entire infrastructure through one portal.

#616 exalate-issue-sync[bot] opened 4 years ago
0
S289: As a DBA, I want to be able to define what tables, columns, and rows are tracked so that my downstream systems can get the data they need

#615 exalate-issue-sync[bot] opened 4 years ago
0
S558: As an admin of the console, I (and only I) can change passwords of any users from the management console, so that we have security permissions for employees who leave the organization or otherwise have transitioned out of the project that require...

#614 exalate-issue-sync[bot] opened 4 years ago
0
S35: As an operator, I want to be able to run analytics work loads on production clusters so that I don't have to set up ETL pipelines and complicated architectures.

#613 exalate-issue-sync[bot] opened 4 years ago
0
S552: As a developer, I want CockroachDB to automatically whitelist my IP so that I don't have to look it up, or forget to whitelist a new location i am in and then not be able to connect to my DB

#612 exalate-issue-sync[bot] opened 4 years ago
0
S291: As a DBA, I want to be able to manage any changes to schemas so that my downstream applications can still ingest and understand streaming updates

#611 exalate-issue-sync[bot] opened 4 years ago
0
S429: As an admin, I want my team members to use only our organization email address to sign up, so that there is no risk of work related information (such as cluster password) going to an employees' personal email inbox.

#610 exalate-issue-sync[bot] opened 4 years ago
0
S292: As a DBA, I want to be able to manage any changes to schemas so that my downstream applications can still ingest and understand streaming updates

#609 exalate-issue-sync[bot] opened 4 years ago
0
S294: As a CRDB user, I want storage options for ideal performance specified to me so that

#608 exalate-issue-sync[bot] opened 4 years ago
0
S165: As a DBA, I want to make sure that other users of my database can only query the portions of a partitioned database that I specify so that I can maintain compliance

#607 exalate-issue-sync[bot] opened 4 years ago
0
S34: As a DBA, I need user and role management so that I can secure my database.

#606 exalate-issue-sync[bot] opened 4 years ago
0
S231: As a DBA, when my streaming pipeline crashes, I want to be able to replay transactions that were lost so that I don’t lose data

#605 exalate-issue-sync[bot] opened 4 years ago
1
S229: As a DBA, when I am setting up streaming architectures, I want to be able to take a snapshot of the existing data in my online DB so that the pipeline I set up incorporates historical data

#604 exalate-issue-sync[bot] opened 4 years ago
1
S103: As a DBA, I want to push database or table updates to a streaming pipeline so that I can further analyze it or store it into a different system for analysis.

#603 exalate-issue-sync[bot] opened 4 years ago
0
S226: As a DBA, I want to be able to define what data should be streamed to downstream systems using filters so that I can minimize the potential impact streaming changes will have on my live production systems.

#602 exalate-issue-sync[bot] opened 4 years ago
1
S228: As a DBA, I need a unified view of changes that occurred across a distributed cluster so that I can duplicate data across multiple systems in consistent, ordered, and transactional manner.

#601 exalate-issue-sync[bot] opened 4 years ago
1
S97: As an operator, I need to know how large my backups and restores will be so that I can provision enough storage to complete the job.

#600 exalate-issue-sync[bot] opened 4 years ago
0
S104: As a DBA, I want to persist database changes to a caching system so that I can keep my caches up to date for faster application performance.

#599 exalate-issue-sync[bot] opened 4 years ago
0
S224: As a DBA, I want to be able to persist changes in the database to downstream indexes that speed up queries for dependent applications so that I can make the most of best-of-breed solutions across the entire infrastructure stack.

#598 exalate-issue-sync[bot] opened 4 years ago
1
S227: As a DBA, when I need my database to talk to other systems in my architecture, I want to access an ordered transaction log so that my other systems can stay up to date with changes in my online transactional database

#597 exalate-issue-sync[bot] opened 4 years ago
0
S98: As a DBA, I want to support point in time rollback so that I can bring development clusters back to a working state to improve the productivity of the development team.

#596 exalate-issue-sync[bot] opened 4 years ago
0
S225: As a DBA, I want to be able to copy in real-time changes from a production database to an analytics (?) database so that any jobs I run on the analytics database do not impact traffic to my live production cluster.

#595 exalate-issue-sync[bot] opened 4 years ago
1
S332: [EPIC]: As a prospective customer, I want a CockroachDB cluster created for me so that I can start using CockroachDB without having to worry about initial set up considerations like which cloud, which version etc.

#594 exalate-issue-sync[bot] opened 4 years ago
1
S331: [EPIC]: As a prospective customer of CockroachDB [details tbd], I want to sign up for a CockroachDB hosted solution so that I can get a cluster up and running as fast as possible and start using the product.

#593 exalate-issue-sync[bot] opened 4 years ago
1
S326: As a developer, I want to be able to send my changefeed directly to AWS S3 and Google Cloud Storage

#592 exalate-issue-sync[bot] opened 4 years ago
0
S334: [EPIC OUT OF SCOPE V1]: As a prospective CockroachDB user, I want to set up appropriate monitoring and alerting for my clusters so that I can be aware of anything that requires my attention.

#591 exalate-issue-sync[bot] opened 4 years ago
1
S333: [EPIC]: As a prospective user, I want a secure way to connect to the CockroachDB cluster that I just created so that I can start using the database and realize the full potential of CockroachDB.

#590 exalate-issue-sync[bot] opened 4 years ago
1
S335: [EPIC]: As a PM, I want to be able to measure everything (TBD exact details) through the entire customer journey so that I can use the data to make better product decisions.

#589 exalate-issue-sync[bot] opened 4 years ago
1
S330: As an administrator, I want to be able to know whether my cluster can tolerate a failure of a node or locality without running out of disk space.

#588 exalate-issue-sync[bot] opened 4 years ago
1
S122: [QA] As a developer I want CockroachDB to provide an insecure single node template so I can quickly (and cheaply) test out non-distributed functionality.

#587 exalate-issue-sync[bot] opened 4 years ago
1
S211: As an operator, I want to know what ranges a given query touches so that I can determine whether or not the query is written efficiently.

#586 exalate-issue-sync[bot] opened 4 years ago
0
S6: As an operator I want to kill long running queries so that they don't impact service level.

#585 exalate-issue-sync[bot] opened 4 years ago
0
S584: As a database

#584 exalate-issue-sync[bot] opened 4 years ago
0
S458: As a developer, I want to get a one node managed CockroachDB cluster using a

#583 exalate-issue-sync[bot] opened 4 years ago
0
S461:

#582 exalate-issue-sync[bot] opened 4 years ago
0
S626: As an application developer, I want to use read locks because I want to completely avoid transaction retry errors.

#581 exalate-issue-sync[bot] opened 4 years ago
0
S627: As an application developer, I want to use read locks to have better performance because I anticipate my new application will experience contentious workloads.

#580 exalate-issue-sync[bot] opened 4 years ago
0
S634: As a PM, I want to be able to query the replication factor of each deployment so that I can audit its usage by customers.

#579 exalate-issue-sync[bot] opened 4 years ago
0
S365: As a Cockroach Cloud PM, I want to understand how many SQL queries were run by each hosted customer, so that I can alert customer success about potential churn due to non-usage

#578 exalate-issue-sync[bot] opened 4 years ago
1
S367: As a CockroachDB PM, I want to know which enterprise features such as zone configs, CDC were used by hosted customers, so that I can understand better the use cases of hosted customers and offer up our expertise to set up the cluster correctly.

#577 exalate-issue-sync[bot] opened 4 years ago
0
S633: As an database performance engineer, I can configure my production application to toggle between 3x and 1x replication so that I can experiment with 1x replication for its cost savings.

#576 exalate-issue-sync[bot] opened 4 years ago
0
S366:

#575 exalate-issue-sync[bot] opened 4 years ago
0
S507: As a developer, I want the SQL invocation to connect to the MSO cluster, so that I can first check if the connection string works before connecting it to my app.

#574 exalate-issue-sync[bot] opened 4 years ago
0

Previous Next