Translate

Saturday, 28 December 2024

What are modes in looker

In Looker, the term "modes" primarily refers to two distinct states that a Looker project can be in: Development Mode and Production Mode. These modes are crucial for managing changes to your LookML code and ensuring a stable environment for your users.

what are modes in looker


1. Development Mode (Dev Mode)

  • For Making Changes: This is where you make changes to your LookML files. You can edit, add, or delete code, experiment with different configurations, and preview the results.
  • Isolated Environment: Changes you make in Development Mode do not affect the production environment. This means that users exploring data in Production Mode will not be impacted by your ongoing development work.
  • Version Control (Git Integration): Looker integrates with Git for version control in Development Mode. This allows you to track changes, collaborate with other developers, and revert to previous versions if needed.
  • How to Enter: You typically toggle into Development Mode by clicking a button or link within the Looker interface.

2. Production Mode

  • For End Users: This is the live, stable version of your Looker instance that end users interact with to explore data, create reports, and view dashboards.
  • Read-Only Project Files: In Production Mode, the LookML project files are read-only. This prevents accidental changes that could disrupt the user experience.
  • Stable Environment: Production Mode provides a consistent and reliable environment for accessing and analyzing data.

Why Two Modes?

The separation of Development and Production Modes is essential for:

  • Preventing Errors: By making changes in an isolated environment, you can test and validate your LookML code before it goes live, minimizing the risk of errors impacting users.
  • Collaboration: Multiple developers can work on different features or changes in Development Mode without interfering with each other or the production environment.
  • Version Control: Git integration allows for proper version control, making it easy to track changes, revert to previous versions, and manage releases.

Workflow

The typical workflow involves:

  1. Switching to Development Mode: When you need to make changes to your LookML, you switch to Development Mode.
  2. Making Changes: You edit the LookML files, previewing the results in the Explore area.
  3. Committing Changes (with Git): Once you're happy with your changes, you commit them to Git.
  4. Deploying to Production: When you're ready to make your changes live, you deploy them to Production Mode. This updates the production environment with your latest LookML code.

In summary: Development Mode is your workspace for making changes, while Production Mode is the stable environment for end users. This separation is a core feature of Looker that ensures a smooth and reliable experience for everyone.

No comments:

Post a Comment

Note: only a member of this blog may post a comment.