Log inSkip to main contentSkip to sidebar
Loading…
Jira
  • Dashboards
  • Projects
  • Issues
  • Give feedback to Atlassian
  • Help
    • Jira Core help
    • Keyboard Shortcuts
    • Issue Reminders help
    • About Jira
    • Jira Credits
  • Log In

Export - CSV (All fields)

Export - CSV (Current fields)

Comma (,) Semicolon (;) Vertical bar (|) Caret (^)

  1. Bug MXS-5482
    Schemarouter only processes the first routing hint
  2. Bug MXS-5152
    Shard map update may hang if no valid servers are available
  3. Bug MXS-3876
    sys schema not ignored by schemarouter
  4. Bug MXS-4471
    Table selection doesn't tolerate node failures
  5. Bug MXS-2608
    debug assert at backend.cc:104 failed: !is_waiting_result()
  6. Bug MXS-1167
    MaxScale tries to connect to internal services when loading database users
  7. Bug MXS-1160
    Load infile not working on Schemarouter
  8. Bug MXS-1820
    SHOW DATABASES only returns lowercase results
  9. Bug MXS-2409
    Schemarouter crashes if PREPARE or EXECUTE is malformed
  10. Bug MXS-2734
    Unexpected error message when preferred_server is configured
  11. Bug MXS-245
    Common function extract_database can give misleading error message
  12. Bug MXS-2962
    Output of 'status' wrong when connected to a backend server via schema router.
  13. New Feature MXS-411
    need to shard by table name
  14. Bug MXS-4983
    Schemarouter monitoring requirements are not documented clearly
  15. Bug MXS-4980
    show shards does not show all information expected
  16. Bug MXS-4966
    mariadb-dump gets an error dumping schemas
  17. Bug MXS-4965
    auth_all_servers should be enabled automatically
  18. Bug MXS-4964
    Simple sharding tutorial is out of date
  19. Bug MXS-4963
    Docu for SchemaRouter Simple Sharding does not work
  20. Bug MXS-4947
    Tables in information_schema are treated as a normal tables
  21. Bug MXS-4527
    Schemarouter reports "non-existent database"
  22. Bug MXS-4503
    schemarouter returns empty response when querying INFORMATION_SCHEMA.TABLES
  23. Sub-Task MXS-4795
    Add catalog support to schemarouter
  24. Bug MXS-5544
    Prepared statements fail through schemarouter for Columnstore
  25. New Feature MXS-5029
    Allow sending commands to all shards
  26. Bug MXS-5027
    Duplicate shard detection cannot be turned off
  27. Bug MXS-4760
    Automatically ignored tables are not documented for schemarouter
  28. Bug MXS-3836
    refresh_databases does nothing
  29. Bug MXS-4273
    command "show shards" or "show databases" encoding output
  30. New Feature MXS-4268
    Add soft and hard TTL to schemarouter
  31. Bug MXS-4152
    Schemarouter performance degrades as the number of tables increases
  32. Bug MXS-4151
    Schemarouter duplicate checks are excessively slow
  33. Bug MXS-4199
    SchemaRouter cannot handle schemas in upper case letters
  34. Bug MXS-3054
    Crash with persistent connections, schemarouter and local services abstracted as servers
  35. New Feature MXS-4116
    Add possibility to choose primary source for schemarouter
  36. Bug MXS-4110
    Schemarouter does not ignore the sys schema
  37. Bug MXS-4092
    schemarouter: duplicate tables found, if table differs on upper lower case only
  38. New Feature MXS-4077
    Show all databases with schemarouter in GUI
  39. Bug MXS-5248
    Debug assertion due to non-existent dcall ID
  40. Bug MXS-5158
    Potential race condition in shard map updating
  41. Bug MXS-2991
    Enable MaxScale SchemaRouter for 'simple' SchemaRouting.
  42. Bug MXS-3892
    schema router flood information schemas with queries
  43. Bug MXS-4243
    EXPLAIN select output differs from cli or direct DB outputs
  44. Bug MXS-4237
    Schemarouter duble free crash
  45. New Feature MXS-4216
    Allow stale cache usage in schemarouter
  46. New Feature MXS-4215
    Allow manual clearing of schemarouter caches
  47. New Feature MXS-4214
    Allow schemarouter caches to be refresh during off-peak hours
  48. Bug MXS-3320
    Schema router times out connections from JDBC/C3P0 when database is defined
  49. Bug MXS-3273
    Connection lost when unrelated server loses Slave status
  50. Bug MXS-3267
    Unexpected result state error when server loses Slave status
Refresh results
{"errorMessages":["jqlTooComplex"],"errors":{}}
[{"id":-1,"name":"My open issues","jql":"assignee = currentUser() AND resolution = Unresolved order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":true},{"id":-2,"name":"Reported by me","jql":"reporter = currentUser() order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":true},{"id":-4,"name":"All issues","jql":"order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-5,"name":"Open issues","jql":"resolution = Unresolved order by priority DESC,updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-9,"name":"Done issues","jql":"statusCategory = Done order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-3,"name":"Viewed recently","jql":"issuekey in issueHistory() order by lastViewed DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-6,"name":"Created recently","jql":"created >= -1w order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-7,"name":"Resolved recently","jql":"resolutiondate >= -1w order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-8,"name":"Updated recently","jql":"updated >= -1w order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false}]
0.3
0
  • Atlassian Jira Project Management Software
  • About Jira
  • Report a problem

Powered by a free Atlassian Jira open source license for MariaDB Corporation Ab. Try Jira - bug tracking software for your team.

Atlassian